From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Fredrik Noring <noring@nocrew.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Improving read/write/close system call reliability when used with pthreads
Date: Sun, 12 Aug 2007 16:13:37 +0100 [thread overview]
Message-ID: <20070812161337.3828381c@the-village.bc.nu> (raw)
In-Reply-To: <70E19A0A-2728-4ADA-B984-A36182C1F575@nocrew.org>
> 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
next prev parent reply other threads:[~2007-08-12 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 13:03 Fredrik Noring
2007-08-12 14:17 ` Paul Jackson
2007-08-12 18:30 ` [PATCH] " Fredrik Noring
2007-08-12 15:13 ` Alan Cox [this message]
2007-08-12 16:33 ` Fredrik Noring
2007-08-12 18:55 ` Alan Cox
2007-08-12 19:19 ` Fredrik Noring
2007-08-13 3:14 ` David Schwartz
2007-08-13 6:50 ` Fredrik Noring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070812161337.3828381c@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=noring@nocrew.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®