From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Dominique MARTINET <dominique.martinet@atmark-techno.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, deller@gmx.de, qemu-stable@nongnu.org
Subject: Re: [PATCH 3/6] linux-user: Adjust brk for load_bias [regression]
Date: Tue, 26 Nov 2024 10:24:12 +0100 [thread overview]
Message-ID: <3f1f56122cde6ac457f774b79fa4ba4113a38a33.camel@linux.ibm.com> (raw)
In-Reply-To: <Z0V0undiZVtHIy7z@atmark-techno.com>
On Tue, 2024-11-26 at 16:11 +0900, Dominique MARTINET wrote:
> This commit is fairly old, but this appears to cause a segfault for
> older versions of ldconfig:
> ```
> $ docker run --rm --platform linux/arm64/v8 -ti
> docker.io/debian:bullseye-slim ldconfig
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> Segmentation fault (core dumped)
> ```
>
> The segfault happens inside ldconfig code (code_gen_buffer in qemu's
> backtrace), so I'm not sure how to debug that further, but it doesn't
> reproduce in bookworm's ldconfig so that is something that was
> "fixed"
> in glibc at some point.
>
> If someone needs to run older debian releases with a newer qemu that
> might be a problem in the future?
>
> [we might need to run old containers once every few years to rebuild
> old
> projects in a similar environment they were built on, so would
> eventually need to work around this problem somehow]
>
>
> The failure can be reproduced just running `qemu-aarch64
> ./path/to/ldconfig` on an extracted container so it was easy to
> bisect
> and I've got down to this commit; hence replying here directly with
> involved people.
> ------
> commit aec338d63bc28f1f13d5e64c561d7f1dd0e4b07e
> Author: Richard Henderson <richard.henderson@linaro.org>
> Date: Wed Aug 16 10:32:18 2023 -0700
>
> linux-user: Adjust brk for load_bias
>
> PIE executables are usually linked at offset 0 and are
> relocated somewhere during load. The hiaddr needs to
> be adjusted to keep the brk next to the executable.
>
> Cc: qemu-stable@nongnu.org
> Fixes: 1f356e8c013 ("linux-user: Adjust initial brk when
> interpreter is close to executable")
> Tested-by: Helge Deller <deller@gmx.de>
> Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ------
>
> I've done my share of debugging linux-user last week[1] so I'll leave
> this
> as is for now, I've downgraded to (a non-static-pie build of) 7.1 for
> our build machine and am not in immediate trouble.
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053101
>
> If this doesn't get much interest I might try to pick at it further
> in
> a couple of weeks, assuming it's something we can/want to fix on qemu
> side.
>
> Thanks,
Hi,
I think this is
https://gitlab.com/qemu-project/qemu/-/issues/1913
Best regards,
Ilya
next prev parent reply other threads:[~2024-11-26 9:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:14 [PATCH 0/6] linux-user: Rewrite open_self_maps Richard Henderson
2023-08-16 18:14 ` [PATCH 1/6] util/selfmap: Use dev_t and ino_t in MapInfo Richard Henderson
2023-08-17 8:52 ` Philippe Mathieu-Daudé
2023-08-16 18:14 ` [PATCH 2/6] linux-user: Use walk_memory_regions for open_self_maps Richard Henderson
2023-08-16 18:14 ` [PATCH 3/6] linux-user: Adjust brk for load_bias Richard Henderson
2023-08-17 8:53 ` Philippe Mathieu-Daudé
2023-08-18 0:16 ` Richard Henderson
2023-08-17 16:04 ` Michael Tokarev
2023-08-18 0:17 ` Richard Henderson
2024-11-26 7:11 ` [PATCH 3/6] linux-user: Adjust brk for load_bias [regression] Dominique MARTINET
2024-11-26 9:24 ` Ilya Leoshkevich [this message]
2024-11-26 9:29 ` Dominique MARTINET
2023-08-16 18:14 ` [PATCH 4/6] linux-user: Show heap address in /proc/pid/maps Richard Henderson
2023-08-21 12:07 ` Philippe Mathieu-Daudé
2023-08-16 18:14 ` [PATCH 5/6] linux-user: Remove ELF_START_MMAP and image_info.start_mmap Richard Henderson
2023-08-17 9:00 ` Philippe Mathieu-Daudé
2023-08-18 0:19 ` Richard Henderson
2023-08-18 0:35 ` Warner Losh
2023-08-16 18:14 ` [PATCH 6/6] linux-user: Show vdso address in /proc/pid/maps Richard Henderson
2023-08-21 12:07 ` Philippe Mathieu-Daudé
2023-08-16 22:25 ` [PATCH 0/6] linux-user: Rewrite open_self_maps Helge Deller
2023-08-17 17:08 ` Ilya Leoshkevich
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=3f1f56122cde6ac457f774b79fa4ba4113a38a33.camel@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=deller@gmx.de \
--cc=dominique.martinet@atmark-techno.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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).