[Bugme-new] [Bug 9149] New: accept() doesn't wake with error when
socket descriptor closed
bugme-daemon at bugzilla.kernel.org
bugme-daemon at bugzilla.kernel.org
Fri Oct 12 07:42:06 PDT 2007
http://bugzilla.kernel.org/show_bug.cgi?id=9149
Summary: accept() doesn't wake with error when socket descriptor
closed
Product: Networking
Version: 2.5
KernelVersion: 2.6.18
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
AssignedTo: shemminger at linux-foundation.org
ReportedBy: mkielar at go2.pl
Most recent kernel where this bug did not occur: no idea
Distribution: no idea - remote server
Hardware Environment: i686
Software Environment: no idea - probably pure console server
Problem Description:
In multithreaded process, one thread launches accept() on a valid-so-far
listening socket file descriptor sockfd and waits on it. After this second
thread launches close( sockfd ). First thread further waits on accept() even
though the descriptor is now invalid. accept() should wake up and return with
-1 and errno EBADF.
Steps to reproduce:
described above
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Bugme-new
mailing list