From: James Morris <jmorris@intercode.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: read/recv sometimes returns EAGAIN instead of EINTR on SMP
Date: Tue, 23 Jul 2002 16:12:12 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0207231528580.17462-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20020723010437.GC2292@conectiva.com.br>
On Mon, 22 Jul 2002, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 23, 2002 at 07:56:39AM +0400, kuznet@ms2.inr.ac.ru escreveu:
> > Second, I never understood what is the problem with SIGURG.
> > That's why it lives untouched.
>
> Andi once described it to me and recently he described it to jamesm that
> has done work on this area, but I think he is busy now and haven't had a
> chance to finish, James?
>
I'm not sure it's the same issue. All I've been doing is consolidating
the existing code and storing user credentials so they are checked at
SIGURG delivery time. This would not change the semantics of syscall
return values or signal delivery order.
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2002-07-23 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 10:43 read/recv sometimes returns EAGAIN instead of EINTR on SMP machines Peter Niemayer
2002-07-23 2:57 ` David S. Miller
2002-07-23 3:56 ` read/recv sometimes returns EAGAIN instead of EINTR on SMP kuznet
2002-07-23 1:04 ` Arnaldo Carvalho de Melo
2002-07-23 6:12 ` James Morris [this message]
2002-07-23 8:12 ` read/recv sometimes returns EAGAIN instead of EINTR on SMP machines David Schwartz
2002-07-23 10:14 ` Peter Niemayer
2002-07-23 10:16 ` read/recv sometimes returns EAGAIN instead of EINTR on SMPmachines Peter Niemayer
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=Mutt.LNX.4.44.0207231528580.17462-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.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®