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 3/4] linux-user: fix reserved_va page leak in do_munmap
Date: Wed, 19 Nov 2025 12:21:54 +0100 [thread overview]
Message-ID: <18f5e9b1-d4f3-4c7c-90ce-aa9ca5032f40@linaro.org> (raw)
In-Reply-To: <20251117170954.31451-4-mlugg@mlugg.co.uk>
On 11/17/25 18:09, Matthew Lugg wrote:
> The old logic had an off-by-one bug. For instance, assuming 4k pages on
> host and guest, if 'len' is '4097' (indicating to unmap 2 pages), then
> 'last = start + 4096', so 'real_last = start + 4095', so ultimately
> 'real_len = 4096'. I do not believe this could cause any observable bugs
> in guests, because `target_munmap` page-aligns the length it passes in.
> However, calls to this function in `target_mremap` do not page-align the
> length, so those calls could "drop" pages, leading to a part of the
> reserved region becoming unmapped. At worst, a host allocation could get
> mapped into that hole, then clobbered by a new guest mapping.
>
> Signed-off-by: Matthew Lugg<mlugg@mlugg.co.uk>
> ---
> linux-user/mmap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2025-11-19 11:22 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
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 [this message]
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=18f5e9b1-d4f3-4c7c-90ce-aa9ca5032f40@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).