From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v3 0/2] linux-user: Fix unaligned memory access in prlimit64 syscall
Date: Fri, 24 Feb 2023 01:39:05 +0100 [thread overview]
Message-ID: <20230224003907.263914-1-iii@linux.ibm.com> (raw)
v2: https://lists.gnu.org/archive/html/qemu-devel/2023-02/msg07017.html
v2 -> v3: Fix __put_user() argument order mixup.
I tested v2 only against sh4, where the original problem was
discovered, but it regresses aarch64.
v1: https://lists.gnu.org/archive/html/qemu-devel/2023-02/msg06999.html
v1 -> v2: Fix by using proper target_rlimit64 alignment (Richard).
Use __get_user() and __put_user() (Philippe - if I understood
the suggestion correctly).
Hi,
Richard reported [1] that the new linux-fork-trap test was failing
under UBSan [2], so it was excluded from the PR.
This is a resend of the test plus the fix for the additional issue that
it uncovered.
[1] https://lists.gnu.org/archive/html/qemu-devel/2023-02/msg06130.html
[2] https://gitlab.com/qemu-project/qemu/-/jobs/3807471447#L5064
Best regards,
Ilya
Ilya Leoshkevich (2):
linux-user: Fix unaligned memory access in prlimit64 syscall
tests/tcg/linux-test: Add linux-fork-trap test
linux-user/generic/target_resource.h | 4 +-
linux-user/syscall.c | 8 ++--
tests/tcg/multiarch/linux/linux-fork-trap.c | 51 +++++++++++++++++++++
3 files changed, 57 insertions(+), 6 deletions(-)
create mode 100644 tests/tcg/multiarch/linux/linux-fork-trap.c
--
2.39.1
next reply other threads:[~2023-02-24 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 0:39 Ilya Leoshkevich [this message]
2023-02-24 0:39 ` [PATCH v3 1/2] linux-user: Fix unaligned memory access in prlimit64 syscall Ilya Leoshkevich
2023-02-24 7:42 ` Philippe Mathieu-Daudé
2023-03-06 21:34 ` Laurent Vivier
2023-03-07 10:32 ` Laurent Vivier
2023-02-24 0:39 ` [PATCH v3 2/2] tests/tcg/linux-test: Add linux-fork-trap test Ilya Leoshkevich
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=20230224003907.263914-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@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 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).