From: Richard Henderson <richard.henderson@linaro.org>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Dario Faggioli" <dfaggioli@suse.com>
Subject: Re: [RFC PATCH] elfload: Fix alignment when unmapping excess reservation
Date: Sat, 15 Feb 2025 11:08:57 -0800 [thread overview]
Message-ID: <5c33021b-7bf4-409e-8ea4-fd2473455adc@linaro.org> (raw)
In-Reply-To: <92d268c0-ba67-454a-b22b-688122eccd7b@linaro.org>
On 2/15/25 11:06, Richard Henderson wrote:
> On 2/13/25 06:35, Fabiano Rosas wrote:
>> When complying with the alignment requested in the ELF and unmapping
>> the excess reservation, having align_end not aligned to the guest page
>> causes the unmap to be rejected by the alignment check at
>> target_munmap and later brk adjustments hit an EEXIST.
>>
>> Fix by aligning the start of region to be unmapped.
>>
>> Fixes: c81d1fafa6 ("linux-user: Honor elf alignment when placing images")
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1913
>> Signed-off-by: Fabiano Rosas <farosas@suse.de>
>> ---
>> In the bug there was mention of the vdso landing in the wrong spot,
>> but I don't see evidence of this in my testing. Looking at the
>> addresses in the bug report, there seems to have been a mistake
>> because I don't see an overlap there either.
>> ---
>> linux-user/elfload.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/linux-user/elfload.c b/linux-user/elfload.c
>> index a2c152e5ad..05ee5e74fd 100644
>> --- a/linux-user/elfload.c
>> +++ b/linux-user/elfload.c
>> @@ -3351,7 +3351,7 @@ static void load_elf_image(const char *image_name, const
>> ImageSource *src,
>> if (align_size != reserve_size) {
>> abi_ulong align_addr = ROUND_UP(load_addr, align);
>> - abi_ulong align_end = align_addr + reserve_size;
>> + abi_ulong align_end = TARGET_PAGE_ALIGN(align_addr + reserve_size);
>> abi_ulong load_end = load_addr + align_size;
>
> Both align_end and load_end must be aligned.
Bah, hit ctrl-enter, not enter. I'll fix and queue.
r~
next prev parent reply other threads:[~2025-02-15 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 14:35 [RFC PATCH] elfload: Fix alignment when unmapping excess reservation Fabiano Rosas
2025-02-15 19:06 ` Richard Henderson
2025-02-15 19:08 ` Richard Henderson [this message]
2025-02-19 7:42 ` Michael Tokarev
2025-02-19 13:05 ` Fabiano Rosas
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=5c33021b-7bf4-409e-8ea4-fd2473455adc@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=dfaggioli@suse.com \
--cc=farosas@suse.de \
--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).