Re: PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread

On Friday 14 July 2006 20:07, Michael Lindner wrote:
> Update: On advice from Nish Aravamudan I upgraded my kernel to 2.6.17.4 and
> verified that the problem still exists in that version.

This behaviour is POSIX compliant and should be expected. There is no bug.

If you want to work around it, use shutdown() as you suggested, and poll() 
instead of select() and wait for POLLNVAL or POLLHUP.

See the following Java "bug" which explains the situation a little better:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4344135

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread
  - From: Michael Lindner <[email protected]>
- Re: PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread
  - From: Michael Lindner <[email protected]>

Prev by Date: Re: Kernel 2.6.17.1 bug/oops in snd_usb_audio subsystem
Next by Date: Re: [PATCHSET] 0/15 IO scheduler improvements
Previous by thread: Re: PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread
Next by thread: RE: PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]