From: Shu-Chun Weng <scw@google.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
Richard Henderson <richard.henderson@linaro.org>,
Shu-Chun Weng <scw@google.com>
Subject: [PATCH v2 0/2] linux-user: openat() fixes
Date: Fri, 8 Dec 2023 12:49:49 -0800 [thread overview]
Message-ID: <20231208204951.552837-1-scw@google.com> (raw)
Since v1:
- Eliminate static buffers in do_guest_openat()
Shu-Chun Weng (2):
linux-user: Define TARGET_O_LARGEFILE for aarch64
linux-user: Fix openat() emulation to not modify atime
linux-user/aarch64/target_fcntl.h | 1 +
linux-user/syscall.c | 47 +++++++++++++++++++++++++------
2 files changed, 39 insertions(+), 9 deletions(-)
next reply other threads:[~2023-12-08 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 20:49 Shu-Chun Weng [this message]
2023-12-08 20:49 ` [PATCH v2 1/2] linux-user: Define TARGET_O_LARGEFILE for aarch64 Shu-Chun Weng
2023-12-08 20:49 ` [PATCH v2 2/2] linux-user: Fix openat() emulation to not modify atime 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=20231208204951.552837-1-scw@google.com \
--to=scw@google.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 NNTP newsgroup(s).