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

> [1.] One line summary of the problem:
> 	close(fd) doesn't wake up read(fd) or select() in another thread

	If you delete a resource in one thread while another thread is using it,
anything can happen. This is as serious a bug as calling 'free' on a block
of memory while another thread is using it.

	You can never be sure the other thread was in 'read' or 'select' (as
opposed to being about to call it and then being pre-empted), so such code
will always have race conditions.

	DS


-
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]>

• Prev by Date: Re: 2.6.18 Headers - Long
• Next by Date: RE: 2.6.17-1.2145_FC5 mmap-related soft lockup
• Previous by thread: Re: PROBLEM: close(fd) doesn't wake up read(fd) or select() in another thread
• Next by thread: [PATCHv2 2.6.18-rc1-mm2 1/3] net: UDP-Lite generic support
• 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]