From: David Holland
> Sent: 29 October 2015 14:59
> On Tue, Oct 27, 2015 at 10:52:46AM +0000, Alan Burlison wrote:
> > >But in general, this is basically a problem with the application: the file
> > >descriptor space is shared between threads and having one thread sniping
> > >at open files, you do have a problem and whatever the kernel does in that
> > >case perhaps doesn't matter all that much: the application needs to be
> > >fixed anyway.
> >
> > The scenario in Hadoop is that the FD is being used by a thread that's
> > waiting in accept and another thread wants to shut it down, e.g. because
> > the application is terminating and needs to stop all threads cleanly.
>
> ISTM that the best way to do this is to post a signal to the thread so
> accept bails with EINTR, at which point it can check to see if it's
> supposed to be exiting.
Actually, just send it a connect indication.
ISTM that the correct call should be listen(fd, 0);
Although that doesn't help a thread stuck in recvmsg() for a datagram.
It is also tempting to think that close(fd) should sleep until all
io activities using that fd have completed - whether or not blocking
calls are woken.
David
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
