Re: Improving read/write/close system call reliability when used with pthreads

> For (1), a simple scenario has two threads: a reader and a watchdog.  
> The reader thread is stuck in a blocking read of an unreliable pipe.  
> The watchdog thread is designed to cancel the blocking read using  
> close on the reader's fd.

The reader still has the fd open so the fd is not yet closed. This seems
completely sane to me. Closing the *writer* fd would create an EOF which
is the proper response.

Alan
-
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/

---

• Follow-Ups:
  • Re: Improving read/write/close system call reliability when used with pthreads
    • From: Fredrik Noring <[email protected]>

• References:
  • Improving read/write/close system call reliability when used with pthreads
    • From: Fredrik Noring <[email protected]>

• Prev by Date: Re: [patch 00/23] Atomic operations updates: add cmpxchg_local
• Next by Date: [patch 0/9] Text Edit Lock
• Previous by thread: Re: [PATCH] Improving read/write/close system call reliability when used with pthreads
• Next by thread: Re: Improving read/write/close system call reliability when used with pthreads
• 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]