From: Laurent Vivier <laurent@vivier.eu>
To: YAMAMOTO Takashi <yamamoto@midokura.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 02/11] linux-user: Fix the execfd case of /proc/self/exe open
Date: Sun, 20 Jun 2021 16:16:06 +0200 [thread overview]
Message-ID: <465df811-e6d8-2bfd-5ebe-1ebf85fa5c99@vivier.eu> (raw)
In-Reply-To: <20210531055019.10149-3-yamamoto@midokura.com>
Le 31/05/2021 à 07:50, YAMAMOTO Takashi a écrit :
> It's problematic to return AT_EXECFD as it is because the user app
> would close it.
> This patch opens it via /proc/self/fd instead.
>
> Signed-off-by: YAMAMOTO Takashi <yamamoto@midokura.com>
> ---
> linux-user/syscall.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index a2b03ecb8b..14a63518e2 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -8118,7 +8118,17 @@ static int do_openat(void *cpu_env, int dirfd, const char *pathname, int flags,
>
> if (is_proc_myself(pathname, "exe")) {
> int execfd = qemu_getauxval(AT_EXECFD);
> - return execfd ? execfd : safe_openat(dirfd, exec_path, flags, mode);
> + if (execfd) {
> + char filename[PATH_MAX];
> + int ret;
> +
> + snprintf(filename, sizeof(filename), "/proc/self/fd/%d", execfd);
> + ret = safe_openat(dirfd, filename, flags, mode);
> + if (ret != -1) {
> + return ret;
> + }
> + }
> + return safe_openat(dirfd, exec_path, flags, mode);
> }
>
> for (fake_open = fakes; fake_open->filename; fake_open++) {
>
I think a dup() would be more appropriate, or explain why not.
Thanks,
Laurent
next prev parent reply other threads:[~2021-06-20 14:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 5:50 [PATCH v2 00/11] linux-user changes to run docker YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 01/11] linux-user: handle /proc/self/exe for execve YAMAMOTO Takashi
2021-06-20 14:14 ` Laurent Vivier
2021-06-21 2:02 ` Takashi Yamamoto
2021-06-22 13:47 ` Laurent Vivier
2021-05-31 5:50 ` [PATCH v2 02/11] linux-user: Fix the execfd case of /proc/self/exe open YAMAMOTO Takashi
2021-06-20 14:16 ` Laurent Vivier [this message]
2021-06-21 1:19 ` Takashi Yamamoto
2021-05-31 5:50 ` [PATCH v2 03/11] linux-user: dup the execfd on start up YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 04/11] linux-user: make exec_path realpath YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 05/11] linux-user: Implement pivot_root YAMAMOTO Takashi
2021-06-20 14:02 ` Laurent Vivier
2021-06-20 14:05 ` Laurent Vivier
2021-05-31 5:50 ` [PATCH v2 06/11] linux-user: add get_exe_path YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 07/11] linux-user: simplify is_proc_myself YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 08/11] linux-user: Implement exec of /proc/$pid/exe of qemu process YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 09/11] linux-user: Make the qemu detection for /proc/$pid/exe a bit conservative YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 10/11] linux-user: a crude hack for libcontainer (CLONE_PARENT) [!MERGE] YAMAMOTO Takashi
2021-05-31 5:50 ` [PATCH v2 11/11] linux-user: always assume preserve_argv0 for now [!MERGE] YAMAMOTO Takashi
2021-05-31 6:07 ` [PATCH v2 00/11] linux-user changes to run docker no-reply
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=465df811-e6d8-2bfd-5ebe-1ebf85fa5c99@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=yamamoto@midokura.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).