This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2 1/3] posix: Remove dynamic memory allocation from execl{e,p}
- From: Florian Weimer <fweimer at redhat dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Tue, 2 Feb 2016 12:24:49 +0100
- Subject: Re: [PATCH v2 1/3] posix: Remove dynamic memory allocation from execl{e,p}
- Authentication-results: sourceware.org; auth=none
- References: <1454343665-1706-1-git-send-email-adhemerval dot zanella at linaro dot org> <1454343665-1706-2-git-send-email-adhemerval dot zanella at linaro dot org> <alpine dot DEB dot 2 dot 10 dot 1602011648030 dot 2674 at digraph dot polyomino dot org dot uk> <56AF936C dot 6070907 at linaro dot org>
On 02/01/2016 06:18 PM, Adhemerval Zanella wrote:
> Right, it is not ensuring the safeness. Is '-fstack-check' the suffice
> option to ensure it or do we need a more strict one?
In my tests, the initial stack banging probe is sometimes more than a
page away from the current stack pointer, so it does not look safe to me.
For posix_spawn, it's probably simpler for now to compute the shell
invocation in the parent. That is, perform two vforks in case the first
execve fails.
Florian