qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Matthew Lugg <mlugg@mlugg.co.uk>, qemu-devel@nongnu.org
Cc: laurent@vivier.eu, peter.maydell@linaro.org
Subject: Re: [PATCH v2 1/4] linux-user: fix mremap unmapping adjacent region
Date: Wed, 19 Nov 2025 12:20:30 +0100	[thread overview]
Message-ID: <277c2bb6-5d24-451c-a45e-893822acd2b0@linaro.org> (raw)
In-Reply-To: <20251117170954.31451-2-mlugg@mlugg.co.uk>

On 11/17/25 18:09, Matthew Lugg wrote:
> This typo meant that calls to `mremap` which shrink a mapping by some N
> bytes would, when the virtual address space was pre-reserved (e.g.
> 32-bit guest on 64-bit host), unmap the N bytes following the*original*
> mapping.
> 
> Signed-off-by: Matthew Lugg<mlugg@mlugg.co.uk>
> ---
>   linux-user/mmap.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> No changes from last revision, just rebased.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~


  reply	other threads:[~2025-11-19 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 17:09 [PATCH v2 0/4] linux-user: fix several mremap bugs Matthew Lugg
2025-11-17 17:09 ` [PATCH v2 1/4] linux-user: fix mremap unmapping adjacent region Matthew Lugg
2025-11-19 11:20   ` Richard Henderson [this message]
2025-11-17 17:09 ` [PATCH v2 2/4] linux-user: fix mremap errors for invalid ranges Matthew Lugg
2025-11-17 17:09 ` [PATCH v2 3/4] linux-user: fix reserved_va page leak in do_munmap Matthew Lugg
2025-11-19 11:21   ` Richard Henderson
2025-11-17 17:09 ` [PATCH v2 4/4] tests: add tcg coverage for fixed mremap bugs Matthew Lugg

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=277c2bb6-5d24-451c-a45e-893822acd2b0@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=laurent@vivier.eu \
    --cc=mlugg@mlugg.co.uk \
    --cc=peter.maydell@linaro.org \
    --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).