Displaying 2 results from an estimated 2 matches for "exevpe".
Did you mean:
execvpe
2023 Feb 22
1
[libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe()
On 2/21/23 20:32, Eric Blake wrote:
> On Tue, Feb 21, 2023 at 07:07:38PM +0100, Laszlo Ersek wrote:
>> Well, given Daniel's comments meanwhile, it seems like the original
>> execvp() is something we shouldn't fret about. :/
>
> glibc marks execvp() and exevpe() as 'MT-Safe env', which means it
> does not modify 'environ' and presumably does not use 'malloc'. If
> the only reason POSIX marks execvp() as thread-unsafe is because of
> its interaction with getenv() for PATH and therefore unsafe to exec a
> child in one t...
2023 Feb 22
1
[libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe()
...32, Eric Blake wrote:
> > On Tue, Feb 21, 2023 at 07:07:38PM +0100, Laszlo Ersek wrote:
>
> >> Well, given Daniel's comments meanwhile, it seems like the original
> >> execvp() is something we shouldn't fret about. :/
> >
> > glibc marks execvp() and exevpe() as 'MT-Safe env', which means it
> > does not modify 'environ' and presumably does not use 'malloc'. If
> > the only reason POSIX marks execvp() as thread-unsafe is because of
> > its interaction with getenv() for PATH and therefore unsafe to exec a
>...