[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f1a37663e.6534e3c91209390.4904049890278199879@soss.website>
Date: Tue, 30 Jun 2026 15:27:46 -0500
From: Skye Soss <skye@...s.website>
To: "musl" <musl@...ts.openwall.com>
Subject: Re: [PATCH] add execveat syscall wrapper
> > The execveat syscall was added to Linux in v4.0 (released in 2015),
>
> added in 3.19 (released in 2015) see
> linux commit 27d6ec7ad6f7a2a131ff8e9f77bcc6547e178d2c
Thanks, I mistakenly used the wrong musl commit message as a reference.
> > and the libc wrapper function was added to glibc in 2021
> >
> > The AT_EXECVEAT_CHECK option was added to Linux 6.14, so I believe the
>
> it's spelled AT_EXECVE_CHECK
> you should add it from linux uapi to musl fcntl.h
> (AT_ is reserved namespace so no need for _GNU_SOURCE)
glibc does not export AT_EXECVE_CHECK from fcntl.h, so users must include
<linux/fcntl.h> even when using glibc. Otherwise, musl's fcntl.h currently
guards some AT_ macros behind _GNU_SOURCE: most importantly AT_EMPTY_PATH,
which is a required flag to pass alongside AT_EXECVE_CHECK.
> > +int execveat(int, const char *, char *const [], char *const [], int);
>
> should be under the _GNU_SOURCE section,
> this is not a posix api.
makes sense, will do
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
