mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: atanaskunchev@proton.me, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Kees Cook <kees@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binfmt_misc: fix typo in "auxiliary vector"
Date: Fri, 23 Oct 2026 10:55:26 -0700	[thread overview]
Message-ID: <26adbb3d-bbd8-442c-aed6-80cf091888b0@infradead.org> (raw)
In-Reply-To: <20261023-binfmt-typo-v1-1-459d4ae4c15f@proton.me>


On 10/23/26 10:50 AM, Atanas Kunchev via B4 Relay wrote:
> From: Atanas Kunchev <atanaskunchev@proton.me>
> 
> Fix "auxilary" -> "auxiliary".
> 
> Signed-off-by: Atanas Kunchev <atanaskunchev@proton.me>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
> Fix a spelling mistake in the binfmt_misc documentation.
> ---
>  Documentation/admin-guide/binfmt-misc.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/binfmt-misc.rst b/Documentation/admin-guide/binfmt-misc.rst
> index 9e84b877d06d..e37668371453 100644
> --- a/Documentation/admin-guide/binfmt-misc.rst
> +++ b/Documentation/admin-guide/binfmt-misc.rst
> @@ -73,7 +73,7 @@ Here is what the fields mean:
>  	    Legacy behavior of binfmt_misc is to pass the full path
>              of the binary to the interpreter as an argument. When this flag is
>              included, binfmt_misc will open the file for reading and pass its
> -            descriptor into the auxilary vector with the key "AT_EXECFD", thus
> +            descriptor into the auxiliary vector with the key "AT_EXECFD", thus
>              allowing the interpreter to execute non-readable binaries. This
>              feature should be used with care - the interpreter has to be trusted
>              not to emit the contents of the non-readable binary.
> 
> ---
> base-commit: 734bef548a96e8774d6eef5dfa2026c6edc4e80b
> change-id: 20261023-binfmt-typo-bf80308e23a0
> 
> Best regards,

-- 
~Randy

  reply	other threads:[~2026-10-23 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 17:50 Atanas Kunchev via B4 Relay
2026-10-23 17:55 ` Randy Dunlap [this message]
2026-10-25 13:22 ` Daniel Pereira
2026-11-02 16:13 ` Jonathan Corbet

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=26adbb3d-bbd8-442c-aed6-80cf091888b0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=atanaskunchev@proton.me \
    --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

all inboxes | Powered by JetHome®