From: Alejandro Colomar <alx@kernel.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: linux-man@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] man/man2/memfd_secret.2: tfix
Date: Sat, 18 Jul 2026 14:08:50 +0200 [thread overview]
Message-ID: <altstsU94cjelV5C@devuan> (raw)
In-Reply-To: <20260713121111.372487-1-stepnem@smrk.net>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
Hi Štěpán,
On 2026-07-13T14:11:11+0200, Štěpán Němec wrote:
> Fixes: ac5edfeb1dd6 (2021-08-27; "memfd_secret.2: New page describing memfd_secret() system call")
> Cc: Mike Rapoport <rppt@linux.ibm.com>
> Signed-off-by: Štěpán Němec <stepnem@smrk.net>
> ---
> On Fri, 10 Jul 2026 18:44:19 +0200
> Alejandro Colomar wrote:
>
> > I think I'd fix this typo in a separate commit, since it's a meaningful
> > typo (both EMFILE and ENFILE exist, and they have a slightly different
> > meaning).
> >
> > In the fix, please include the following tags:
> >
> > Fixes: ac5edfeb1dd6 (2021-08-27; "memfd_secret.2: New page describing memfd_secret() system call")
> > Cc: Mike Rapoport <rppt@linux.ibm.com>
>
> Fair enough.
>
> FWIW, out of abundance of caution (admittedly verging on paranoia), I
> did verify that unprivileged memfd_secret distinguished EMFILE and
> ENFILE as expected (brought about by setrlimit for the former and
> limiting fs.file-max for the latter in a VM running a recent alpine-edge
> image) before sending the original patch, but the hypothesis that this
> was anything other than a typo or a copy-paste error seemed too
> far-fetched to mention that.
Thanks! I've applied the patch.
Have a lovely day!
Alex
>
> man/man2/memfd_secret.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man2/memfd_secret.2 b/man/man2/memfd_secret.2
> index 0ea4b8e93c37..4033adc75772 100644
> --- a/man/man2/memfd_secret.2
> +++ b/man/man2/memfd_secret.2
> @@ -119,7 +119,7 @@ .SH ERRORS
> .B EMFILE
> The per-process limit on the number of open file descriptors has been reached.
> .TP
> -.B EMFILE
> +.B ENFILE
> The system-wide limit on the total number of open files has been reached.
> .TP
> .B ENOMEM
>
> --
> 2.55.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-18 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:34 [PATCH 1/3] man/: tfix Štěpán Němec
2026-07-09 15:34 ` [PATCH 2/3] man/man7/pipe.7: Note kernel commit of the soft limit triggered cap increase Štěpán Němec
2026-07-10 16:46 ` Alejandro Colomar
2026-07-09 15:34 ` [PATCH 3/3] man/man7/landlock.7: wfix Štěpán Němec
2026-07-10 16:48 ` Alejandro Colomar
2026-07-13 11:48 ` Štěpán Němec
2026-07-18 12:17 ` Alejandro Colomar
2026-07-10 16:44 ` [PATCH 1/3] man/: tfix Alejandro Colomar
2026-07-13 12:11 ` [PATCH] man/man2/memfd_secret.2: tfix Štěpán Němec
2026-07-18 12:08 ` Alejandro Colomar [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=altstsU94cjelV5C@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--cc=stepnem@smrk.net \
/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