From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Matthew Lugg <mlugg@mlugg.co.uk>,
qemu-devel@nongnu.org, laurent@vivier.eu, qemu-stable@nongnu.org
Subject: Re: [PATCH 0/4] linux-user: fix several mremap bugs
Date: Mon, 17 Nov 2025 11:46:13 +0000 [thread overview]
Message-ID: <CAFEAcA_Ee=tzECheOSN21fwqQgL9wwGEUYbGrnTS6B5kZYYxgA@mail.gmail.com> (raw)
In-Reply-To: <a794dd06-cf28-4d04-be08-c87796296a72@tls.msk.ru>
On Mon, 17 Nov 2025 at 11:43, Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> On 11/17/25 14:42, Peter Maydell wrote:
> > On Mon, 17 Nov 2025 at 08:40, Michael Tokarev <mjt@tls.msk.ru> wrote:
> >>
> >> A friendly ping? Has this series been forgotten?
> >> It looks like it should be picked up for 10.2 release.
> >
> > No, there are review comments on the series that need to be
> > addressed before it can be applied.
>
> Yes that's what I actually mean, - just used the wrong wording.
> What I mean is that this series is better be fixed and applied
> before/for 10.2.
It would be nice, but AFAIK they're not regressions.
Patch 1 is reviewed and could be applied, I guess.
thanks
-- PMM
next prev parent reply other threads:[~2025-11-17 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 20:03 [PATCH 0/4] linux-user: fix several mremap bugs Matthew Lugg
2025-10-11 20:03 ` [PATCH 1/4] linux-user: fix mremap unmapping adjacent region Matthew Lugg
2025-10-20 15:08 ` Peter Maydell
2025-10-21 19:44 ` Richard Henderson
2025-10-11 20:03 ` [PATCH 2/4] linux-user: fix mremap errors for invalid ranges Matthew Lugg
2025-10-20 15:10 ` Peter Maydell
2025-10-21 19:50 ` Richard Henderson
2025-10-11 20:03 ` [PATCH 3/4] linux-user: fix reserved_va page leak in do_munmap Matthew Lugg
2025-10-20 16:00 ` Peter Maydell
2025-11-17 15:06 ` Matthew Lugg
2025-10-21 19:57 ` Richard Henderson
2025-10-11 20:03 ` [PATCH 4/4] tests: add tcg coverage for fixed mremap bugs Matthew Lugg
2025-10-11 20:15 ` Matthew Lugg
2025-10-20 15:26 ` Peter Maydell
2025-11-17 15:13 ` Matthew Lugg
2025-11-17 15:30 ` Matthew Lugg
2025-11-17 8:40 ` [PATCH 0/4] linux-user: fix several " Michael Tokarev
2025-11-17 11:42 ` Peter Maydell
2025-11-17 11:43 ` Michael Tokarev
2025-11-17 11:46 ` Peter Maydell [this message]
2025-11-17 11:51 ` Michael Tokarev
2025-11-17 11:54 ` mlugg
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='CAFEAcA_Ee=tzECheOSN21fwqQgL9wwGEUYbGrnTS6B5kZYYxgA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=mlugg@mlugg.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).