From: Helge Deller <deller@gmx.de>
To: Richard Henderson <richard.henderson@linaro.org>,
Andreas Schwab <schwab@suse.de>,
Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: make sure brk(0) returns a page-aligned value
Date: Sun, 9 Jul 2023 08:12:48 +0200 [thread overview]
Message-ID: <ce6660a7-e878-0e36-3cc2-ba3de1dbdea6@gmx.de> (raw)
In-Reply-To: <9bde924d-55c6-9254-e7c9-6cbf7b7c9b5a@gmx.de>
On 7/8/23 23:36, Helge Deller wrote:
> On 7/8/23 19:26, Richard Henderson wrote:
>> On 7/6/23 12:34, Andreas Schwab wrote:
>>> Fixes: 86f04735ac ("linux-user: Fix brk() to release pages")
>>> Signed-off-by: Andreas Schwab <schwab@suse.de>
>>> ---
>>> linux-user/syscall.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>>> index 08162cc966..e8a17377f5 100644
>>> --- a/linux-user/syscall.c
>>> +++ b/linux-user/syscall.c
>>> @@ -805,7 +805,7 @@ static abi_ulong brk_page;
>>> void target_set_brk(abi_ulong new_brk)
>>> {
>>> - target_brk = new_brk;
>>> + target_brk = TARGET_PAGE_ALIGN(new_brk);
>>> brk_page = HOST_PAGE_ALIGN(target_brk);
>>> }
...
>> I'm curious why this error might have produced host memory clobbering, but I'm not going to debug that.
> I don't believe that this un-alignment triggers host memory clobbering either.
See my follow-up in the other mail threadd:
"Re: [RISC-V] ERROR:../accel/tcg/cpu-exec.c:1028:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)"
Helge
next prev parent reply other threads:[~2023-07-09 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 11:34 [PATCH] linux-user: make sure brk(0) returns a page-aligned value Andreas Schwab
2023-07-08 17:26 ` Richard Henderson
2023-07-08 21:36 ` Helge Deller
2023-07-09 6:12 ` Helge Deller [this message]
2023-07-12 20:40 ` Helge Deller
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=ce6660a7-e878-0e36-3cc2-ba3de1dbdea6@gmx.de \
--to=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=schwab@suse.de \
/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).