From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: "Alexandra Hájková via Libc-alpha" <libc-alpha@sourceware.org>,
"Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: [PATCH] Linux: Add execveat system call wrapper
Date: Tue, 28 Apr 2020 15:03:06 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2004281500020.21260@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87lfmfpudv.fsf@mid.deneb.enyo.de>
On Tue, 28 Apr 2020, Florian Weimer wrote:
> * Alexandra Hájková via Libc-alpha:
>
> > diff --git a/sysdeps/mach/hurd/i386/libc.abilist b/sysdeps/mach/hurd/i386/libc.abilist
> > index 60696d827f..571c281b06 100644
> > --- a/sysdeps/mach/hurd/i386/libc.abilist
> > +++ b/sysdeps/mach/hurd/i386/libc.abilist
> > @@ -2182,6 +2182,7 @@ GLIBC_2.3.4 xdr_quad_t F
> > GLIBC_2.3.4 xdr_u_quad_t F
> > GLIBC_2.30 twalk_r F
> > GLIBC_2.32 mach_print F
> > +GLIBC_2.32 execveat F
> > GLIBC_2.32 thrd_current F
> > GLIBC_2.32 thrd_equal F
> > GLIBC_2.32 thrd_sleep F
> > diff --git a/sysdeps/unix/sysv/linux/Makefile b/sysdeps/unix/sysv/linux/Makefile
>
> This is not correct because you are not adding execveat for Hurd. You
> can just remove that change.
First, the commit message should discuss the rationale for this being a
Linux-specific interface in glibc, as opposed to an OS-independent
interface with an ENOSYS stub for OSes that don't implement it. The
interface looks quite generic like the POSIX *at interfaces, so there's a
reasonable case for it being an OS-independent interface (which doesn't
require adding an implementation for Hurd, an ENOSYS stub in a suitable
OS-independent directory would suffice, along with the declaration, test
etc. being OS-independent).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-04-28 15:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:20 Alexandra Hájková
2020-04-28 14:17 ` Florian Weimer
2020-04-28 15:03 ` Joseph Myers [this message]
2020-04-28 15:03 ` Joseph Myers
2020-04-28 15:08 ` Florian Weimer
2020-04-28 15:29 ` Joseph Myers
2020-04-28 17:15 ` Florian Weimer
2020-04-28 17:19 ` Joseph Myers
2020-04-28 17:44 ` Adhemerval Zanella
2020-04-28 17:50 ` Florian Weimer
2020-04-28 18:31 ` Adhemerval Zanella
2020-04-30 11:15 ` Florian Weimer
2020-04-30 12:28 ` Adhemerval Zanella
2020-04-30 12:55 ` Florian Weimer
2020-04-30 19:03 ` Adhemerval Zanella
2020-04-30 12:32 ` Adhemerval Zanella
2020-11-06 21:03 ` Alexandra Hájková
2020-11-06 22:15 ` Joseph Myers
2020-11-09 18:43 ` Florian Weimer
2020-11-09 21:34 ` Yann Droneaud
2020-11-26 11:31 ` Alexandra Petlanova Hajkova
2020-11-09 20:39 ` Adhemerval Zanella
2020-12-03 13:55 ` Florian Weimer
2020-11-26 21:28 ` Alexandra Hájková
2020-11-27 14:58 ` Adhemerval Zanella
2020-11-27 17:32 ` Florian Weimer
2020-11-27 17:38 ` Adhemerval Zanella
2020-12-03 14:20 ` Alexandra Hájková
2020-12-03 14:37 ` Andreas Schwab
2020-12-08 14:44 ` Adhemerval Zanella
2020-12-08 15:18 ` Florian Weimer
2020-12-08 16:41 ` Adhemerval Zanella
2021-03-15 21:42 ` Alexandra Hájková
2021-03-15 22:12 ` Joseph Myers
2021-03-15 22:17 ` Dmitry V. Levin
2021-03-24 13:54 ` Alexandra Hájková
2021-03-26 20:36 ` Adhemerval Zanella
2021-04-02 12:13 ` Alexandra Hájková
2021-04-02 13:29 ` Adhemerval Zanella
2021-04-05 16:32 ` Alexandra Hájková
2021-04-12 10:26 ` Alexandra Hájková
2021-04-12 11:14 ` Andreas Schwab
2021-04-12 19:26 ` Alexandra Hájková
2021-04-13 19:27 ` Adhemerval Zanella
2021-04-21 18:11 ` Alexandra Hájková
2021-05-03 19:20 ` Adhemerval Zanella
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=alpine.DEB.2.21.2004281500020.21260@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ahajkova@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).