public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: jeremy.linton@arm.com, Jakub Jelinek <jakub@redhat.com>,
	Jeff Law <law@redhat.com>, Carlos O'Donell <carlos@redhat.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] aarch64: update NEWS about branch protection
Date: Wed, 29 Jul 2020 12:04:54 +0200	[thread overview]
Message-ID: <878sf2r60p.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200729091734.GT7127@arm.com> (Szabolcs Nagy's message of "Wed,  29 Jul 2020 10:17:34 +0100")

* Szabolcs Nagy:

>> Are there any ELF notes I should watch out for?
>
> readelf should show
>
>   GNU                  0x00000010       NT_GNU_PROPERTY_TYPE_0        Properties: AArch64 feature: BTI
>
> (PAC may be missing in some libgcc asm, that's
> fixed up in gcc-trunk, but it's harmless.)

Thanks.  It looks like with the flags in CFLAGS, the notes are indeed
there in some cases, because RPM debugedit chokes on them:

explicitly decompress any DWARF compressed ELF sections in /builddir/build/BUILDROOT/glibc-2.31.9000-23.fc33.aarch64/usr/bin/gencat
extracting debug info from /builddir/build/BUILDROOT/glibc-2.31.9000-23.fc33.aarch64/usr/bin/gencat
Failed to update file: invalid section entry size

I'll try to figure out what is going on there.  It's a bit suspicious
that this is the first dynamically linked binary, so maybe the notes are
missing from the shared objects and statically linked binaries still.

Thanks,
Florian


  reply	other threads:[~2020-07-29 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  8:08 Szabolcs Nagy
2020-07-29  8:11 ` Florian Weimer
2020-07-29  8:49   ` Szabolcs Nagy
2020-07-29  9:01     ` Florian Weimer
2020-07-29  9:17       ` Szabolcs Nagy
2020-07-29 10:04         ` Florian Weimer [this message]
2020-07-29 10:25           ` Szabolcs Nagy
2020-07-29 12:51         ` Florian Weimer
2020-07-31  6:58         ` Szabolcs Nagy
2020-07-31 13:22           ` Szabolcs Nagy
2020-08-03 18:53 ` Carlos O'Donell

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=878sf2r60p.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=jakub@redhat.com \
    --cc=jeremy.linton@arm.com \
    --cc=law@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=szabolcs.nagy@arm.com \
    /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).