From: Randy Dunlap <rdunlap@infradead.org>
To: Alexey Dobriyan <adobriyan@gmail.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] ELF: document some de-facto PT_* ABI quirks
Date: Tue, 14 Mar 2023 19:34:11 -0700 [thread overview]
Message-ID: <e262ea00-a027-9073-812e-7e034d75e718@infradead.org> (raw)
In-Reply-To: <2acb586c-08a9-42d9-a41e-7986cc1383ea@p183>
Hi,
[adding linux-doc for other interested parties]
On 3/14/23 10:02, Alexey Dobriyan wrote:
> Turns out rules about PT_INTERP, PT_GNU_STACK and PT_GNU_PROPERTY
> segment headers are slightly different.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> Documentation/ELF/ELF.rst | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/ELF/ELF.rst
> @@ -0,0 +1,28 @@
> +.. SPDX-License-Identifier: GPL-2.0
According to Documentation/doc-guide/sphinx.rst, "=" underlines are used
for chapters (by convention).
And could the document have a title, like:
=========================
ELF header usage in Linux
=========================
(I just made that up. Feel free to change it. :)
Also, the .rst file should be added to some chapter in the current
documentation tree, such as under "Other documentation", so add this file name
to Documentation/staging/index.rst. In fact this file could live in
Documentation/staging instead of in Documentation/ELF/ (IMO of course).
> +
> +Definitions
> +===========
> +
> +"First" program header is the one with the smallest offset in the file:
> +e_phoff. "Last" program header is the one with the biggest offset:
> +e_phoff + (e_phnum - 1) * sizeof(Elf_Phdr).
> +
> +PT_INTERP
> +=========
> +
> +First PT_INTERP program header is used to locate the filename of ELF
> +interpreter. Other PT_INTERP headers are ignored (since Linux 2.4.11).
> +
> +PT_GNU_STACK
> +============
> +
> +Last PT_GNU_STACK program header defines userspace stack executability
> +(since Linux 2.6.6). Other PT_GNU_STACK headers are ignored.
> +
> +PT_GNU_PROPERTY
> +===============
> +
> +ELF interpreter's last PT_GNU_PROPERTY program header is used (since
> +Linux 5.8). If interpreter doesn't have one, then the last PT_GNU_PROPERTY
> +program header of an executable is used. Other PT_GNU_PROPERTY headers
> +are ignored.
Thanks.
--
~Randy
next parent reply other threads:[~2023-03-15 2:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2acb586c-08a9-42d9-a41e-7986cc1383ea@p183>
2023-03-15 2:34 ` Randy Dunlap [this message]
2023-03-17 8:22 ` [PATCH] ELF: document some de-facto PT_* ABI quirks Bagas Sanjaya
2023-03-17 16:53 ` Alexey Dobriyan
2023-03-19 12:52 ` Bagas Sanjaya
2023-03-26 16:49 ` [PATCH v2] " Alexey Dobriyan
2023-03-26 19:51 ` Randy Dunlap
2023-03-29 16:40 ` Jonathan Corbet
2023-04-15 17:37 ` [PATCH v3] " Alexey Dobriyan
2023-04-20 16:07 ` Jonathan Corbet
2023-12-06 22:58 ` Kees Cook
2023-12-07 15:03 ` Eric W. Biederman
2023-12-10 11:45 ` Alexey Dobriyan
2023-12-10 22:58 ` Eric W. Biederman
2023-12-11 16:26 ` Alexey Dobriyan
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=e262ea00-a027-9073-812e-7e034d75e718@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).