public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guillaume.gardet at arm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27068] New: Static binaries SIGILL when BTI is enabled on aarch64
Date: Mon, 14 Dec 2020 08:26:46 +0000 [thread overview]
Message-ID: <bug-27068-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27068
Bug ID: 27068
Summary: Static binaries SIGILL when BTI is enabled on aarch64
Product: glibc
Version: 2.32
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: guillaume.gardet at arm dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Created attachment 13050
--> https://sourceware.org/bugzilla/attachment.cgi?id=13050&action=edit
add_bti_landing_pad.patch
While testing BTI on openSUSE Tumbleweed on aarch64, it showed a SIGILL error
while running ldconfig, which is statically compiled.
To workaround/fix the problem, I applied the attached patch which add a BTI
landing pad for static binaries, with PIC enabled.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-14 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 8:26 guillaume.gardet at arm dot com [this message]
2020-12-14 12:53 ` [Bug libc/27068] " adhemerval.zanella at linaro dot org
2020-12-14 15:32 ` nsz at gcc dot gnu.org
2020-12-15 9:47 ` [Bug libc/27068] Static PIE " nsz at gcc dot gnu.org
2020-12-15 14:30 ` cvs-commit at gcc dot gnu.org
2021-01-21 16:04 ` cvs-commit at gcc dot gnu.org
2021-03-29 8:55 ` nsz at gcc dot gnu.org
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=bug-27068-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).