From: Jonathan Corbet <corbet@lwn.net>
To: Alexey Dobriyan <adobriyan@gmail.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v3] ELF: document some de-facto PT_* ABI quirks
Date: Thu, 20 Apr 2023 10:07:48 -0600 [thread overview]
Message-ID: <87fs8utu3v.fsf@meer.lwn.net> (raw)
In-Reply-To: <88d3f1bb-f4e0-4c40-9304-3843513a1262@p183>
Alexey Dobriyan <adobriyan@gmail.com> writes:
> Turns out rules about PT_INTERP, PT_GNU_STACK and PT_GNU_PROPERTY
> program headers are slightly different.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> v3: move to Documentation/userspace-api/
> v2: integrate into documentation build system
>
> Documentation/userspace-api/ELF.rst | 34 ++++++++++++++++++++++++++++++++++
> Documentation/userspace-api/index.rst | 1 +
> 2 files changed, 35 insertions(+)
Applied, thanks.
jon
next prev parent reply other threads:[~2023-04-20 16:07 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 ` [PATCH] ELF: document some de-facto PT_* ABI quirks Randy Dunlap
2023-03-17 8:22 ` 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 [this message]
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=87fs8utu3v.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).