public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Charlie Jenkins <thecharlesjenkins@gmail.com>
To: Kees Cook <kees@kernel.org>
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: Thu, 23 Apr 2026 00:04:13 -0700	[thread overview]
Message-ID: <20260423070413.GA156309@inky.localdomain> (raw)
In-Reply-To: <202604211026.C462A59EC0@keescook>

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

      reply	other threads:[~2026-04-23  7:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19  4:11 [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag 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 ` [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag Kees Cook
2026-04-23  7:04   ` Charlie Jenkins [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=20260423070413.GA156309@inky.localdomain \
    --to=thecharlesjenkins@gmail.com \
    --cc=corbet@lwn.net \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=skhan@linuxfoundation.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