From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: qemu-x86_64, buster /sbin/ldconfig and setup_arg_pages (a mind dump)
Date: Fri, 17 Jan 2020 08:10:54 -1000 [thread overview]
Message-ID: <3ff41cb9-8d7e-7013-a846-1a9a809bf6f5@linaro.org> (raw)
In-Reply-To: <874kwukmxr.fsf@linaro.org>
On 1/17/20 7:33 AM, Alex Bennée wrote:
> So what do we take away from this?
>
> * we need testcases to exercise the memory layout of dynamic binaries
> * "special" dynamic binaries can break our careful memory layout
> * I feel as though I've trodden on a nest of vipers
>
> Does any of this track with you? What is different about ldconfig that
> breaks our memory placement?
We've been through this bug before, but never came to a resolution. See
https://bugs.launchpad.net/qemu/+bug/1749393
https://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html
r~
prev parent reply other threads:[~2020-01-17 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 17:33 qemu-x86_64, buster /sbin/ldconfig and setup_arg_pages (a mind dump) Alex Bennée
2020-01-17 18:10 ` Richard Henderson [this message]
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=3ff41cb9-8d7e-7013-a846-1a9a809bf6f5@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--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).