From: kuznet@ms2.inr.ac.ru
To: torvalds@osdl.org (Linus Torvalds)
Cc: akpm@osdl.org, Andries.Brouwer@cwi.nl,
linux-kernel@vger.kernel.org (Kernel Mailing List),
netdev@oss.sgi.com, davem@redhat.com (David S. Miller),
kuznet@ms2.inr.ac.ru
Subject: Re: Linux 2.6.0-test9
Date: Mon, 27 Oct 2003 22:36:21 +0300 (MSK) [thread overview]
Message-ID: <200310271936.WAA07348@yakov.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0310261607230.3157-100000@home.osdl.org> from "Linus Torvalds" at Oct 26, 2003 04:21:59 PM
Hello!
> And Alexey apparently tried to do the "FIXME" part, but without thinking
> about the SIGURG part.
Actually, it was thought a lot for several linux-2.x. :-)
> We _need_ to stop at urgent data and we _should_ return -EINTR, and let
> the SIGURG handler do the URG read. Otherwise we'll lose urgent data (or
> we'll just read it inline without realizing that it was urgent data).
The patch was expected not to break this property. Alas, something
is overlooked yet. I still do not understand what exactly is broken,
I feel I have to find some rlogin to experiment in vivo.
Alexey
next prev parent reply other threads:[~2003-10-27 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 19:40 Linux 2.6.0-test9 Andries.Brouwer
2003-10-27 0:01 ` Andrew Morton
2003-10-27 0:21 ` Linus Torvalds
2003-10-27 0:28 ` Linus Torvalds
2003-10-27 6:43 ` David S. Miller
2003-10-27 19:54 ` kuznet
2003-10-27 19:36 ` kuznet [this message]
2003-10-28 0:42 ` Tommy Christensen
2003-10-28 18:25 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 1:48 Andries.Brouwer
2003-10-27 2:10 ` Linus Torvalds
2003-10-27 9:40 ` David S. Miller
2003-10-27 9:47 Mikael Pettersson
2003-10-27 10:58 Andries.Brouwer
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=200310271936.WAA07348@yakov.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).