From: Michael Matz <matz@suse.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Rich Felker <dalias@libc.org>, Cary Coutant <ccoutant@gmail.com>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Szabolcs Nagy <nsz@port70.net>,
Jan Beulich <JBeulich@suse.com>,
Binutils <binutils@sourceware.org>,
gnu-gabi@sourceware.org
Subject: Re: RFC: Add GNU_PROPERTY_NEED_PHDRS
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1810021504450.7867@wotan.suse.de> (raw)
In-Reply-To: <CAMe9rOq38bLRyNMaMDfdbK=NvFg2YxEwSL3SERL=iapPZ+4COg@mail.gmail.com>
Hi,
On Tue, 2 Oct 2018, H.J. Lu wrote:
> A .note.gnu.property section will lead to a read-only data PT_LOAD segment
> as the first PT_LOAD segment:
Yes, and it's a hack. This section isn't necessary, it merely is the
easiest (?) way you found to force ld to create the PT_LOAD segment you
want. What about linker scripts that filter out all .note sections? You
_still_ want the phdrs to be mapped in that case. You basically replace
the current state (where the phdrs are mapped by accident) with a
different state that still only works by accident. It would be better to
make this work by design not accident.
Ciao,
Michael.
>
> [hjl@gnu-17 ld]$ readelf -WlS tmpdir/pr23428
> There are 16 section headers, starting at offset 0x2ed0:
>
> Section Headers:
> [Nr] Name Type Address Off Size
> ES Flg Lk Inf Al
> [ 0] NULL 0000000000000000 000000
> 000000 00 0 0 0
> [ 1] .note.gnu.property NOTE 0000000000400158 000158
> 000030 00 A 0 0 8
> [ 2] .text PROGBITS 0000000000401000 001000
> 0000ea 00 AX 0 0 16
> [ 3] .rodata PROGBITS 0000000000402000 002000
> 000006 01 AMS 0 0 1
> [ 4] .comment PROGBITS 0000000000000000 002006
> 00002d 01 MS 0 0 1
> [ 5] .debug_aranges PROGBITS 0000000000000000 002040
> 000060 00 0 0 16
> [ 6] .debug_info PROGBITS 0000000000000000 0020a0
> 0002f7 00 0 0 1
> [ 7] .debug_abbrev PROGBITS 0000000000000000 002397
> 000137 00 0 0 1
> [ 8] .debug_line PROGBITS 0000000000000000 0024ce
> 0001a7 00 0 0 1
> [ 9] .debug_frame PROGBITS 0000000000000000 002678
> 000040 00 0 0 8
> [10] .debug_str PROGBITS 0000000000000000 0026b8
> 0002a1 01 MS 0 0 1
> [11] .debug_loc PROGBITS 0000000000000000 002959
> 000295 00 0 0 1
> [12] .debug_ranges PROGBITS 0000000000000000 002bee
> 000020 00 0 0 1
> [13] .symtab SYMTAB 0000000000000000 002c10
> 0001e0 18 14 14 8
> [14] .strtab STRTAB 0000000000000000 002df0
> 000030 00 0 0 1
> [15] .shstrtab STRTAB 0000000000000000 002e20
> 0000ab 00 0 0 1
> Key to Flags:
> W (write), A (alloc), X (execute), M (merge), S (strings), I (info),
> L (link order), O (extra OS processing required), G (group), T (TLS),
> C (compressed), x (unknown), o (OS specific), E (exclude),
> l (large), p (processor specific)
>
> Elf file type is EXEC (Executable file)
> Entry point 0x4010c0
> There are 5 program headers, starting at offset 64
>
> Program Headers:
> Type Offset VirtAddr PhysAddr
> FileSiz MemSiz Flg Align
> LOAD 0x000000 0x0000000000400000 0x0000000000400000
> 0x000188 0x000188 R 0x1000
> LOAD 0x001000 0x0000000000401000 0x0000000000401000
> 0x0000ea 0x0000ea R E 0x1000
> LOAD 0x002000 0x0000000000402000 0x0000000000402000
> 0x000006 0x000006 R 0x1000
> NOTE 0x000158 0x0000000000400158 0x0000000000400158
> 0x000030 0x000030 R 0x8
> GNU_STACK 0x000000 0x0000000000000000 0x0000000000000000
> 0x000000 0x000000 RWE 0x10
>
> Section to Segment mapping:
> Segment Sections...
> 00 .note.gnu.property
> 01 .text
> 02 .rodata
> 03 .note.gnu.property
> 04
> [hjl@gnu-17 ld]$
>
>
>
next prev parent reply other threads:[~2018-10-02 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz [this message]
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Alan Modra
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Alan Modra
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Rich Felker
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Alan Modra
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=alpine.LSU.2.21.1810021504450.7867@wotan.suse.de \
--to=matz@suse.de \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=ccoutant@gmail.com \
--cc=dalias@libc.org \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nsz@port70.net \
/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).