diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 1998-09-29 12:15:08 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 1998-09-29 12:15:08 +0000 |
commit | 766ed7c0f132488646599d0cd73a25ffe1eecf34 (patch) | |
tree | 0c1f6656e0fa957ef59ce29e0fc3e3c55fcfc159 /c/src/lib/libcpu/sh/sh7032 | |
parent | Added sentence to indicate sections were deliberately empty. (diff) | |
download | rtems-766ed7c0f132488646599d0cd73a25ffe1eecf34.tar.bz2 |
Patch from Eric Norum <eric@skatter.usask.ca>:
Remember the test to see if a socket could be read and written at
the same time by two different tasks? I discovered that if both
tasks attempt to close the socket a panic can occur from inside the
BSD code.
Closing the same socket twice from two different threads is
certainly an error, but a panic is not the greatest error reporting
method :-)
The following small change to the socket close routine should reduce
the chances of the panic.
Diffstat (limited to 'c/src/lib/libcpu/sh/sh7032')
0 files changed, 0 insertions, 0 deletions