From: Richard Henderson <richard.henderson@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: laurent@vivier.eu, sir@cmpwn.com, philmd@linaro.org
Subject: Re: [PATCH v3] linux-user/syscall: Implement execve without execveat
Date: Thu, 6 Jul 2023 09:07:05 +0100 [thread overview]
Message-ID: <30be90c8-ad32-10fd-d821-49a355536f88@linaro.org> (raw)
In-Reply-To: <696064fd-0509-b4d9-ff93-f60385fb00d0@linaro.org>
On 7/6/23 08:30, Pierrick Bouvier wrote:
>> I guess we'll quickly get a build-time error if there's no host execve syscall
>> (which looks to be, eventually, compat-only).
>>
>
> Out of curiosity, is there any plan for deprecation (or removal) of execve on a specific
> architecture? I thought it had to stay there, just for backward compatibility.
Not on an existing architecture, but the next new one could in theory only implement
execveat. Compare with open, which is not implemented by aarch64 and newer, only openat.
r~
prev parent reply other threads:[~2023-07-06 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 12:10 [PATCH v3] linux-user/syscall: Implement execve without execveat Pierrick Bouvier
2023-07-05 15:26 ` Michael Tokarev
2023-07-05 15:46 ` Richard Henderson
2023-07-06 7:30 ` Pierrick Bouvier
2023-07-06 8:07 ` Richard Henderson [this message]
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=30be90c8-ad32-10fd-d821-49a355536f88@linaro.org \
--to=richard.henderson@linaro.org \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sir@cmpwn.com \
/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 NNTP newsgroup(s).