From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Shu-Chun Weng <scw@google.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
Richard Henderson <richard.henderson@linaro.org>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Jonah Petri <jonah@petri.us>,
Edoardo Spadolini <edoardo.spadolini@gmail.com>
Subject: Re: [PATCH 2/2] linux-user: Fix openat() emulation to not modify atime
Date: Fri, 1 Dec 2023 13:42:07 +0100 [thread overview]
Message-ID: <63d6f19a-ec9b-4397-bf90-95e89a618838@linaro.org> (raw)
In-Reply-To: <20231201032140.2470599-3-scw@google.com>
Hi Shu-Chun,
On 1/12/23 04:21, Shu-Chun Weng wrote:
> Commit b8002058 strengthened openat()'s /proc detection by calling
> realpath(3) on the given path, which allows various paths and symlinks
> that points to the /proc file system to be intercepted correctly.
>
> Using realpath(3), though, has a side effect that it reads the symlinks
> along the way, and thus changes their atime. The results in the
> following code snippet already get ~now instead of the real atime:
>
> int fd = open("/path/to/a/symlink", O_PATH | O_NOFOLLOW);
> struct stat st;
> fstat(fd, st);
> return st.st_atime;
>
> This change opens a path that doesn't appear to be part of /proc
> directly and checks the destination of /proc/self/fd/n to determine if
> it actually refers to a file in /proc.
>
> Neither this nor the existing code works with symlinks or indirect paths
> (e.g. /tmp/../proc/self/exe) that points to /proc/self/exe because it
> is itself a symlink, and both realpath(3) and /proc/self/fd/n will
> resolve into the location of QEMU.
Does this fix any of the following issues?
https://gitlab.com/qemu-project/qemu/-/issues/829
https://gitlab.com/qemu-project/qemu/-/issues/927
https://gitlab.com/qemu-project/qemu/-/issues/2004
> Signed-off-by: Shu-Chun Weng <scw@google.com>
> ---
> linux-user/syscall.c | 42 +++++++++++++++++++++++++++++++++---------
> 1 file changed, 33 insertions(+), 9 deletions(-)
next prev parent reply other threads:[~2023-12-01 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 3:21 [PATCH 0/2] linux-user: openat() fixes Shu-Chun Weng
2023-12-01 3:21 ` [PATCH 1/2] linux-user: Define TARGET_O_LARGEFILE for aarch64 Shu-Chun Weng
2023-12-01 12:38 ` [PATCH-for-8.2? " Philippe Mathieu-Daudé
2023-12-03 13:28 ` [PATCH " Laurent Vivier
2023-12-01 3:21 ` [PATCH 2/2] linux-user: Fix openat() emulation to not modify atime Shu-Chun Weng
2023-12-01 12:42 ` Philippe Mathieu-Daudé [this message]
2023-12-01 18:51 ` Shu-Chun Weng
2023-12-04 13:39 ` Philippe Mathieu-Daudé
2023-12-04 15:34 ` Stefan Hajnoczi
2023-12-01 17:09 ` Helge Deller
2023-12-04 16:58 ` Daniel P. Berrangé
2023-12-08 20:52 ` Shu-Chun Weng
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=63d6f19a-ec9b-4397-bf90-95e89a618838@linaro.org \
--to=philmd@linaro.org \
--cc=edoardo.spadolini@gmail.com \
--cc=jonah@petri.us \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=scw@google.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).