From: Mark Brown <broonie@kernel.org>
To: Sebastian Ott <sebott@redhat.com>
Cc: "Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org
Subject: Re: aarch64 binaries using nolibc segfault before reaching the entry point
Date: Wed, 13 Sep 2023 20:17:01 +0100 [thread overview]
Message-ID: <11356b6c-3f26-411c-a2ce-9cae9dfd3ea5@sirena.org.uk> (raw)
In-Reply-To: <5d49767a-fbdc-fbe7-5fb2-d99ece3168cb@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Wed, Sep 13, 2023 at 08:44:59PM +0200, Sebastian Ott wrote:
> the tpidr2 selftest on an arm box segfaults before reaching the entry point.
> I have no clue what is to blame for this or how to debug it but for a
> statically linked binary there shouldn't be much stuff going on besides the
> elf loader?
I did notice this on some systems but didn't manage to reproduce it
interactively and hence debug it yet :/
> After playing around with linker options I found that using -static-pie
> lets the binaries run successful.
...
> All on aarch64 running fedora37 + upstream kernel. Any hints on what could
> be borken here or how to actually fix it?
That suggests that there's some randomisation of the executable location
going on which is triggering the issue... TBH it seems sensible to take
a patch that enables that for now, it's clearly better to get the tests
running more reliably even if we don't fully understand the issue.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-13 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 18:44 Sebastian Ott
2023-09-13 19:17 ` Mark Brown [this message]
2023-09-13 20:19 ` Thomas Weißschuh
2023-09-13 20:58 ` Willy Tarreau
2023-09-13 21:23 ` Thomas Weißschuh
2023-09-13 21:30 ` Sebastian Ott
2023-09-13 23:02 ` Thomas Weißschuh
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=11356b6c-3f26-411c-a2ce-9cae9dfd3ea5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=sebott@redhat.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®