From: Ulrich Drepper <drepper@redhat.com>
To: dean gaudet <dean@arctic.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, tglx@linutronix.de, torvalds@linux-foundation.org
Subject: Re: [PATCHv2 4/4] first use of sys_indirect system call
Date: Fri, 16 Nov 2007 10:59:50 -0800 [thread overview]
Message-ID: <473DE8A6.2090100@redhat.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0711161021420.15441@twinlark.arctic.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
dean gaudet wrote:
> i'm not suggesting the library set the global flag. i'm suggesting that
> me as an app writer will do so.
>
> it seems like both methods are useful.
No, the global flag is hardly ever useful. You almost never know the
details of all the libraries you link to well enough to determine that
they don't need FD_CLOEXEC disabled. Even more problematic, you cannot
know whether they will need it in future.
For applications the solution is simple: wrap to appropriate calls.
Apache has all these apr_ wrappers. But them to some good news after all.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHPeim2ijCOnn/RHQRAu8xAJsF/0Ir1PWMbHkVRaI5vKOGFS4tMACfVEs9
pMYAiCAU1E2B+7QR0EP+/F8=
=btt9
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-11-16 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 18:22 [PATCHv2 4/4] first use of sys_indirect system call Ulrich Drepper
2007-11-16 2:57 ` Eric Dumazet
2007-11-16 18:08 ` dean gaudet
2007-11-16 18:19 ` Ulrich Drepper
2007-11-16 18:22 ` dean gaudet
2007-11-16 18:59 ` Ulrich Drepper [this message]
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=473DE8A6.2090100@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dean@arctic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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