From: Linus Torvalds <torvalds@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Ulrich Drepper <drepper@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Date: Thu, 31 May 2007 12:59:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705311256230.26602@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705311205520.30485@alien.or.mcafeemobile.com>
On Thu, 31 May 2007, Davide Libenzi wrote:
>
> What I meant, was that the vast majority of MT+exec apps wants all their
> fds (but an handfull, maybe) to be O_CLOEXEC. So a global,
> non-inheritable, per-process flag seemed the most straightforward
> solution.
I'm with Uli on this one. "Stateful" stuff is bad. It's essentially
impossible to handle with libraries - either the library would have to
explciitly always turn the state the way _it_ needs it, or the library
will do the wrogn thing.
For example, what about libraries that are used to set up stdin/stdout for
the forker?
This is not unlike floating point rounding. Having stateful rounding (like
the i387) is *stupid*. You want per-operation rounding (where *one* of the
choices may be "use default"). Exactly because libraries etc will need to
control their _own_ internal choices.
Linus
next prev parent reply other threads:[~2007-05-31 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:09 Ulrich Drepper
2007-05-31 18:22 ` Nicholas Miell
2007-05-31 18:32 ` Ulrich Drepper
2007-05-31 18:35 ` Davide Libenzi
2007-05-31 18:42 ` Ulrich Drepper
2007-05-31 18:46 ` Davide Libenzi
2007-05-31 18:53 ` Ulrich Drepper
2007-05-31 19:02 ` Jakub Jelinek
2007-05-31 19:17 ` Davide Libenzi
2007-05-31 19:50 ` Ulrich Drepper
2007-05-31 20:23 ` Davide Libenzi
2007-05-31 19:59 ` Linus Torvalds [this message]
2007-05-31 23:20 ` Andrew Morton
2007-06-01 1:05 ` Stephen Rothwell
2007-06-01 1:38 ` Stephen Rothwell
2007-06-01 3:07 ` Kyle McMartin
2007-06-01 19:17 ` Byron Stanoszek
2007-06-01 22:55 ` Kyle McMartin
2007-06-10 2:29 ` dean gaudet
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=alpine.LFD.0.98.0705311256230.26602@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®