From: Michael Vogt <michael.vogt@gmail.com>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
Laurent Vivier <laurent@vivier.eu>,
Michael Vogt <mvogt@redhat.com>
Subject: [PATCH v5 0/1] linux-user: add openat2 support in linux-user
Date: Thu, 19 Sep 2024 21:46:44 +0200 [thread overview]
Message-ID: <cover.1726774207.git.mvogt@redhat.com> (raw)
Hi,
This is v5 of the openat2 support in linux-user. Thanks for the
excellent feedback from Laurent Vivier on v4.
This version is very close to v4 and only tweaks/simplifies based
on the code review comments from Laurent, see the below changes
for details.
Thanks again,
Michael
v4 -> v5
- drop "*use_returned_fd" from maybe_do_fake_open() and use return value
-2 to signal to the caller to continue
- keep "pathname" in parameter to do_guest_openat() for a cleaner diff
- fix two missing get_errno(fd)
v3 -> v4:
- fix typos in the commit message
v2 -> v3:
- fix coding style (braches)
- improve argument args/naming in do_openat2()
- merge do_openat2/do_guest_openat2
- do size checks first in do_openat2
- add "copy_struct_from_user" and use in "do_openat2()"
- drop using openat2.h and create "struct open_how_v0"
- log if open_how guest struct is bigger than our supported struct
v1 -> v2:
- do not include <sys/syscall.h>
- drop do_guest_openat2 from qemu.h and make static
- drop "safe" from do_guest_openat2
- ensure maybe_do_fake_open() is correct about when the result should
be used or not
- Extract do_openat2() helper from do_syscall1()
- Call user_unlock* if a lock call fails
- Fix silly incorrect use of "target_open_how" when "open_how" is required
- Fix coding style comments
- Fix validation of arg4 in openat2
- Fix missing zero initialization of open_how
- Define target_open_how with abi_* types
- Warn about unimplemented size if "size" of openat2 is bigger than
target_open_how
Michael Vogt (1):
linux-user: add openat2 support in linux-user
linux-user/syscall.c | 107 +++++++++++++++++++++++++++++++++++++-
linux-user/syscall_defs.h | 7 +++
2 files changed, 112 insertions(+), 2 deletions(-)
--
2.45.2
reply other threads:[~2024-09-19 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1726774207.git.mvogt@redhat.com \
--to=michael.vogt@gmail.com \
--cc=laurent@vivier.eu \
--cc=mvogt@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.