From: Ulrich Drepper <drepper@redhat.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Date: Thu, 31 May 2007 11:53:51 -0700 [thread overview]
Message-ID: <465F19BF.80005@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705311144290.30485@alien.or.mcafeemobile.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/31/2007 Davide Libenzi wrote:
> I was talking for a broader usage, not only glibc centric. Most ppl
> writing MT+exec apps wants all but (eventually) and handfull of files
> leaking across the exec boundary.
Policies are not the answer. Using such a flag is no big issue. *Iff*
we should end up with some form of private file descriptors changing the
default for them would be OK, too. But the existing semantics mustn't
be touched, even if it is selectable. Trying to fix existing buggy code
this way is foolish since it might just as well break assumptions in the
same program.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGXxm/2ijCOnn/RHQRAm+wAJ9YD6KsS6T96xChZvS/3yCwCo6+0gCgl0IY
y6OxxUcuQ8yGJsiYebkuIMY=
=tkxV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-31 18:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:09 [PATCH] Introduce O_CLOEXEC (take >2) 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 [this message]
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
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=465F19BF.80005@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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