From: Denis Vlasenko <vda.linux@googlemail.com>
To: davids@webmaster.com
Cc: "Philippe Troin" <phil@fifi.org>, linux-kernel@vger.kernel.org
Subject: Re: O_NONBLOCK setting "leak" outside of a process??
Date: Sun, 4 Feb 2007 02:22:13 +0100 [thread overview]
Message-ID: <200702040222.13337.vda.linux@googlemail.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKGEJJBFAC.davids@webmaster.com>
On Sunday 04 February 2007 01:55, David Schwartz wrote:
>
> > That's a bug, right? I couldn't find anything to that effect in IEEE
> > Std. 1003.1, 2004 Edition...
> >
> > Ciao,
> > Roland
>
> It's not a bug, there's no rational alternative. What would two indepedent
> file descriptors for the same end of a TCP connection be?
Easy. O_NONBLOCK should only affect whether read/write blocks or
returns EAGAIN. It's logical for this setting to be per-process.
Currently changing O_NONBLOCK on stdin/out/err affects other,
possibly unrelated processes - they don't expect that *their*
reads/writes will start returning EAGAIN!
Worse, it cannot be worked around by dup() because duped fds
are still sharing O_NONBLOCK. How can I work around this?
--
vda
next prev parent reply other threads:[~2007-02-04 1:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 20:52 O_NONBLOCK setting "leak" outside of a process?? Denis Vlasenko
2007-01-30 3:40 ` Philippe Troin
2007-02-01 23:00 ` Denis Vlasenko
2007-02-01 23:15 ` Philippe Troin
2007-02-02 12:10 ` Roland Kuhn
2007-02-02 13:48 ` Guillaume Chazarain
2007-02-02 15:04 ` Roland Kuhn
2007-02-02 18:59 ` Philippe Troin
2007-02-05 10:49 ` bert hubert
2007-02-04 0:55 ` David Schwartz
2007-02-04 1:22 ` Denis Vlasenko [this message]
2007-02-04 7:56 ` David Schwartz
2007-02-04 20:11 ` Michael Tokarev
2007-02-04 21:08 ` David Schwartz
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=200702040222.13337.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@fifi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.