From: Richard Henderson <richard.henderson@linaro.org>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/4] linux-user: Fix shmat(NULL) for h != g
Date: Tue, 26 Mar 2024 19:55:00 -1000 [thread overview]
Message-ID: <12d255ff-476e-4e39-a8bc-4878d8d34447@linaro.org> (raw)
In-Reply-To: <20240325192436.561154-1-iii@linux.ibm.com>
On 3/25/24 09:22, Ilya Leoshkevich wrote:
> v1: https://lore.kernel.org/qemu-devel/20240325153313.526888-1-iii@linux.ibm.com/
> v1 -> v2: Remove an unnecessary ifdef, add R-Bs (Richard).
>
> Hi,
>
> I noticed that while shmat() now works with /proc/self/maps,
> shmat(NULL) got broken. This series fixes that along with two related
> strace issues, and adds a test.
>
> Best regards,
> Ilya
>
>
> Ilya Leoshkevich (4):
> linux-user: Fix semctl() strace
> linux-user: Fix shmat() strace
> linux-user: Fix shmat(NULL) for h != g
> tests/tcg: Test shmat(NULL)
>
> linux-user/mmap.c | 2 +-
> linux-user/strace.c | 10 ++----
> tests/tcg/multiarch/linux/linux-shmat-null.c | 38 ++++++++++++++++++++
> 3 files changed, 42 insertions(+), 8 deletions(-)
> create mode 100644 tests/tcg/multiarch/linux/linux-shmat-null.c
>
Queued, thanks.
r~
prev parent reply other threads:[~2024-03-27 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 19:22 [PATCH v2 0/4] linux-user: Fix shmat(NULL) for h != g Ilya Leoshkevich
2024-03-25 19:22 ` [PATCH v2 1/4] linux-user: Fix semctl() strace Ilya Leoshkevich
2024-03-25 19:23 ` [PATCH v2 2/4] linux-user: Fix shmat() strace Ilya Leoshkevich
2024-03-25 19:23 ` [PATCH v2 3/4] linux-user: Fix shmat(NULL) for h != g Ilya Leoshkevich
2024-03-25 19:23 ` [PATCH v2 4/4] tests/tcg: Test shmat(NULL) Ilya Leoshkevich
2024-03-27 5:55 ` Richard Henderson [this message]
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=12d255ff-476e-4e39-a8bc-4878d8d34447@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=iii@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).