From: LemonBoy <thatlemon@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, laurent@vivier.eu
Subject: [PATCH 0/2] linux-user: Small fix for copy_file_range
Date: Mon, 3 May 2021 19:41:57 +0200 [thread overview]
Message-ID: <20210503174159.54302-1-thatlemon@gmail.com> (raw)
From: Giuseppe Musacchio <thatlemon@gmail.com>
An unwanted sign-extension is currently making the host kernel return EOVERFLOW
when calling copy_file_range with a count of 0xffffffff, despite the host being
a 64bit platform.
The fix is only affecting 32bit targets on 64bit hosts, it's a no-op when the
target bitness matches the host one.
As a bonus add a pretty-printer for copy_file_range syscall.
Giuseppe Musacchio (2):
linux-user: Add copy_file_range to strace.list
linux-user: Fix erroneous conversion in copy_file_range
linux-user/strace.list | 3 +++
linux-user/syscall.c | 3 ++-
2 files changed, 5 insertions(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2021-05-03 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 17:41 LemonBoy [this message]
2021-05-03 17:41 ` [PATCH 1/2] linux-user: Add copy_file_range to strace.list LemonBoy
2021-05-03 18:42 ` Laurent Vivier
2021-05-03 17:41 ` [PATCH 2/2] linux-user: Fix erroneous conversion in copy_file_range LemonBoy
2021-05-03 18:47 ` Laurent Vivier
2021-05-15 19:49 ` [PATCH 0/2] linux-user: Small fix for copy_file_range Laurent Vivier
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=20210503174159.54302-1-thatlemon@gmail.com \
--to=thatlemon@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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.