From: Kees Cook <kees@kernel.org>
To: Charlie Jenkins <thecharlesjenkins@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag
Date: Tue, 21 Apr 2026 10:29:07 -0700 [thread overview]
Message-ID: <202604211026.C462A59EC0@keescook> (raw)
In-Reply-To: <20260419-binfmt_misc_doc_update_p-v1-0-757c12f33cc2@gmail.com>
On Sun, Apr 19, 2026 at 12:11:01AM -0400, Charlie Jenkins wrote:
> Improve the wording of the description of the "P" flag to explain that
> the interpreter gets the path to the file provided by execve and not the
> full path as well as documenting that AT_FLAGS can be read to see if the
> "P" flag is set.
Thanks for the clarifications! I'll get this into the execve tree once
the merge window is over. (I usually wait for -rc2 to be released.)
(Or maybe this should go via linux-doc? I should add this file to the
EXEC entry in MAINTAINERS...)
How did you happen across this mismatch(?weakness?) in the docs?
-Kees
--
Kees Cook
prev parent reply other threads:[~2026-04-21 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 4:11 Charlie Jenkins
2026-04-19 4:11 ` [PATCH 1/2] Documentation/binfmt-misc.rst: Include AT_FLAGS info in "P" flag description Charlie Jenkins
2026-04-19 4:11 ` [PATCH 2/2] Documenation/binfmt-misc.rst: Make "P" flag path desc more precise Charlie Jenkins
2026-04-21 17:29 ` Kees Cook [this message]
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=202604211026.C462A59EC0@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.org \
--cc=thecharlesjenkins@gmail.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