* Re: [Bugme-new] [Bug 9149] New: accept() doesn't wake with error when socket descriptor closed
[not found] <bug-9149-10286@http.bugzilla.kernel.org/>
@ 2007-10-12 17:06 ` Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2007-10-12 17:06 UTC (permalink / raw)
To: mkielar; +Cc: bugme-daemon, netdev
On Fri, 12 Oct 2007 07:42:06 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> 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@linux-foundation.org
> ReportedBy: mkielar@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.
>
I have a feeling this is an FAQ, but I forget what the answer is?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-10-12 17:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <bug-9149-10286@http.bugzilla.kernel.org/>
2007-10-12 17:06 ` [Bugme-new] [Bug 9149] New: accept() doesn't wake with error when socket descriptor closed Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).