From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libebl: Handle aarch64 bti, pac bits in gnu property note
Date: Mon, 07 Sep 2020 12:54:18 +0200 [thread overview]
Message-ID: <18710404d9886b5b558d8647e3452db1d326f9c3.camel@klomp.org> (raw)
In-Reply-To: <c51737bcba0896e4353bfd3b98af89241a62e490.camel@klomp.org>
On Thu, 2020-09-03 at 17:28 +0200, Mark Wielaard wrote:
> On Thu, 2020-09-03 at 11:56 +0200, Mark Wielaard wrote:
> > When building with gcc -mbranch-protection= we might get a gnu property
> > note indicating BTI (Branch Target Identification) and/or PAC (Pointer
> > Authentication Code) is being used.
> >
> > Add a small testcase to show eu-readelf -n now properly lists those
> > bits in the gnu property note.
>
> Oops. Forgot to add the new testfile to EXTRA_DIST.
>
> diff --git a/tests/ChangeLog b/tests/ChangeLog
> index cb2e9956..61c6cb7c 100644
> --- a/tests/ChangeLog
> +++ b/tests/ChangeLog
> @@ -2,6 +2,8 @@
>
> * testfile-gnu-property-note-aarch64.bz2: New file.
> * run-readelf-n.sh: Handle testfile-gnu-property-note-aarch64.
> + * Makefile.am (EXTRA_DIST): Add
> + testfile-gnu-property-note-aarch64.bz2.
Pushed with this addition.
prev parent reply other threads:[~2020-09-07 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:56 Mark Wielaard
2020-09-03 15:28 ` Mark Wielaard
2020-09-07 10:54 ` Mark Wielaard [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=18710404d9886b5b558d8647e3452db1d326f9c3.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@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).