public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: generic-abi@googlegroups.com
Cc: gnu-gabi@sourceware.org
Subject: Re: What integer type should ELF note header have?
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <1513941724.3236.32.camel@klomp.org> (raw)
In-Reply-To: <CAMe9rOrAFX5gPCB355A=vP0VpWQT1x8V3Hrttxm5ZRsvG1FXXw@mail.gmail.com>

On Fri, 2017-12-15 at 08:52 -0800, H.J. Lu wrote:
> > On Fri, Dec 15, 2017 at 8:37 AM, Mark Wielaard <mark@klomp.org> wrote:
> > But honestly it feels much cleaner to just leave this past mistake be.
> > And maybe just introduce new notes types if people really care about
> > having naturally aligned note data in 64-bit ELF files.
> 
> If NT_GNU_PROPERTY_TYPE_0 note is the only concern, I have
> updated all of its REAL consumers to handle it properly.  It is OK if a tool
> doesn't understand it.

It is not really OK. I have seen code that marks an ELF file as invalid
and/or gives up processing ELF notes if it contains notes that don't
follow the standard 4-byte alignment/layout rules. So this really
impacts any tool that processes any ELF note.

> However, if we want to add SHT_NOTE64/PT_NOTE64, please do it ASAP
> since NT_GNU_PROPERTY_TYPE_0 note is used for Intel CET.

Yes, I think that is the correct long term solution. But we might not
get consensus soon over the holiday season. So if you probably should
do something that doesn't require introducing new note layout/alignment
or new note section/phdr types.

The simplest really is to just use the normal note alignment/layout.
This seems to be what Fedora rawhide toolchain currently does for
NT_GNU_PROPERTY_TYPE_0. That way all tools can process the note and the
only thing you need to be careful for is that some values in the note
descriptor might not be naturally aligned. This really shouldn't be an
issue, especially not if this is x86-only anyway.

If you insist on having the data value be naturally aligned for this
one property then it might make sense to look if you can use an
existing ELF construct that does give those guarantees. e.g. Use a
special symbol, PT header or DT value to encode the property.

Cheers,

Mark

  parent reply	other threads:[~2017-12-22 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMe9rOoV5u263JotP=XpiYEzcnjCJOG3U-0X5bnK-WwZoOKTQA@mail.gmail.com>
     [not found] ` <99c8440b-54d8-41bc-6e4d-cd1894536bb7@Oracle.COM>
     [not found]   ` <CAJimCsHE8cMY8MY=BYyQ+o4b14LtQKa2u+SiXWi1o4zBQB9t9Q@mail.gmail.com>
2017-01-01  0:00     ` Suprateeka R Hegde
2017-01-01  0:00       ` Ali Bahrami
2017-01-01  0:00         ` Mark Wielaard
2017-01-01  0:00           ` H.J. Lu
2017-01-01  0:00             ` Mark Wielaard
2017-01-01  0:00               ` H.J. Lu
2017-01-01  0:00                 ` Mark Wielaard
2017-01-01  0:00                   ` H.J. Lu
2017-01-01  0:00                     ` Mark Wielaard
2017-01-01  0:00                       ` H.J. Lu
     [not found]                   ` <3704867e-58b8-3da1-2b29-959ad67a540d@Oracle.COM>
     [not found]                     ` <1513355861.15696.95.camel@klomp.org>
     [not found]                       ` <CAMe9rOrAFX5gPCB355A=vP0VpWQT1x8V3Hrttxm5ZRsvG1FXXw@mail.gmail.com>
2017-01-01  0:00                         ` Mark Wielaard [this message]
     [not found]                           ` <CAMe9rOosYw=9kF8eTUnxwQXNguvCrcK5GSaM=vbUUSA6+J49Zw@mail.gmail.com>
2017-01-01  0:00                             ` Mark Wielaard
2017-01-01  0:00       ` Ali Bahrami

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=1513941724.3236.32.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=generic-abi@googlegroups.com \
    --cc=gnu-gabi@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).