[PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag

Charlie Jenkins posted 2 patches 1 month, 4 weeks ago
Documentation/admin-guide/binfmt-misc.rst | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
[PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag
Posted by Charlie Jenkins 1 month, 4 weeks ago
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.

Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
---
Charlie Jenkins (2):
      Documentation/binfmt-misc.rst: Include AT_FLAGS info in "P" flag description
      Documenation/binfmt-misc.rst: Make "P" flag path desc more precise

 Documentation/admin-guide/binfmt-misc.rst | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)
---
base-commit: 028ef9c96e96197026887c0f092424679298aae8
change-id: ${change-id}

- Charlie
Re: [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag
Posted by Kees Cook 1 month, 3 weeks ago
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
Re: [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag
Posted by Charlie Jenkins 1 month, 3 weeks ago
On Tue, Apr 21, 2026 at 10:29:07AM -0700, Kees Cook wrote:
> 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?

I was writing an interpreter application that was using binfmt-misc and
was using this documentation to do so. I was getting unexpected results
so I read through the kernel code to figure out what was going on.

- Charlie

> 
> -Kees
> 
> -- 
> Kees Cook