public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26926] aarch64: library dependencies are not bti protected
Date: Thu, 21 Jan 2021 10:43:40 +0000 [thread overview]
Message-ID: <bug-26926-131-orvgIquyZC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26926-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26926
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.32/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=610e2c515045a5924f28d8c4fb0a5ddacc90980a
commit 610e2c515045a5924f28d8c4fb0a5ddacc90980a
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Fri Nov 20 15:27:06 2020 +0000
aarch64: Fix missing BTI protection from dependencies [BZ #26926]
The _dl_open_check and _rtld_main_check hooks are not called on the
dependencies of a loaded module, so BTI protection was missed on
every module other than the main executable and directly dlopened
libraries.
The fix just iterates over dependencies to enable BTI.
Fixes bug 26926.
(cherry picked from commit 72739c79f61989a76b7dd719f34fcfb7b8eadde9)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-01-21 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 11:28 [Bug dynamic-link/26926] New: " nsz at gcc dot gnu.org
2020-12-01 12:15 ` [Bug dynamic-link/26926] " nsz at gcc dot gnu.org
2020-12-11 15:19 ` cvs-commit at gcc dot gnu.org
2020-12-11 15:54 ` nsz at gcc dot gnu.org
2021-01-21 10:43 ` cvs-commit at gcc dot gnu.org [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=bug-26926-131-orvgIquyZC@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).