Re: For the almost 4-year anniversary: O_CLOEXEC again
From: Davide Libenzi (davidel_at_xmailserver.org)
Date: 03/29/04
- Previous message: lml_at_beonline.com.au: "Kernel / Userspace Data Transfer"
- In reply to: Ulrich Drepper: "For the almost 4-year anniversary: O_CLOEXEC again"
- Next in thread: dean gaudet: "Re: For the almost 4-year anniversary: O_CLOEXEC again"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Mar 2004 19:14:31 -0800 (PST) To: Ulrich Drepper <drepper@redhat.com>
On Sun, 28 Mar 2004, Ulrich Drepper wrote:
> The proposed solution is simple and already implemented on some systems
> (QNX, BeOS, maybe more). Beside the definition of O_CLOEXEC the
> untested patch below should be all that's needed.
What does prevent a fork() to hit you right before set_close_on_exec()?
Shouldn't we have an install-and-set?
(Personally I manually handle the fork child's code in my MT apps, when
I'm going to exec untrusted apps. Manually here mean close all open fds > 2)
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: lml_at_beonline.com.au: "Kernel / Userspace Data Transfer"
- In reply to: Ulrich Drepper: "For the almost 4-year anniversary: O_CLOEXEC again"
- Next in thread: dean gaudet: "Re: For the almost 4-year anniversary: O_CLOEXEC again"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
