Re: [PATCH 1/3] man/: tfix

Alejandro Colomar <[email protected]> Fri, 10 Jul 2026 18:44:19 +0200
Newsgroups	org.kernel.vger.linux-man
Message-ID	<alEfVXgJBmtlCtH0@devuan>
[CC += Mike]
[CC += Mickaël, Günther]

Hi Štěpán!

On 2026-07-09T17:34:20+0200, Štěpán Němec wrote:
> Signed-off-by: Štěpán Němec <[email protected]>
> ---
>  man/man2/dup.2               | 2 +-
>  man/man2/memfd_secret.2      | 2 +-
>  man/man2/sched_setaffinity.2 | 2 +-
>  man/man2/seccomp_unotify.2   | 2 +-
>  man/man2/select.2            | 2 +-
>  man/man2/send.2              | 2 +-
>  man/man2/sigsuspend.2        | 2 +-
>  man/man5/proc_meminfo.5      | 2 +-
>  man/man7/landlock.7          | 4 ++--
>  man/man7/pipe.7              | 2 +-
>  man/man7/socket.7            | 2 +-
>  11 files changed, 12 insertions(+), 12 deletions(-)
> 

[...]

> 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

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 <[email protected]>

>  The system-wide limit on the total number of open files has been reached.
>  .TP
>  .B ENOMEM

[...]

> diff --git a/man/man7/landlock.7 b/man/man7/landlock.7
> index 55cd002d5789..293374ed9b46 100644
> --- a/man/man7/landlock.7
> +++ b/man/man7/landlock.7
> @@ -21,7 +21,7 @@ .SH DESCRIPTION
>  and unexpected or malicious behaviors in applications.
>  .P
>  A Landlock security policy is a set of access rights
> -(e.g., open a file in read-only, make a directory, etc.)
> +(e.g., open a file read-only, make a directory, etc.)
>  tied to a file hierarchy.
>  Such policy can be configured and enforced by processes for themselves
>  using three system calls:
> @@ -334,7 +334,7 @@ .SS Bind mounts and OverlayFS
>  contains its own set of files and directories,
>  which is different from a bind mount.
>  A policy restricting an OverlayFS layer will not restrict
> -the resulted merged hierarchy, and vice versa.
> +the resulting merged hierarchy, and vice versa.
>  Landlock users should then only think about file hierarchies they want to
>  allow access to, regardless of the underlying filesystem.
>  .\"

This seems to also exist in the kernel internal documentation.  I've
CCd the maintainers of that documentation.

	$ find Documentation/ | grep landlock | xargs grep OverlayFS
	Documentation/userspace-api/landlock.rst:Bind mounts and OverlayFS
	Documentation/userspace-api/landlock.rst:An OverlayFS mount point consists of upper and lower layers.  These layers are
	Documentation/userspace-api/landlock.rst:on the upper layer.  From a Landlock policy point of view, all OverlayFS layers
	Documentation/userspace-api/landlock.rst:OverlayFS layer will not restrict the resulted merged hierarchy, and vice versa.

[...]


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>
signature.asc (application/pgp-signature, 833 B)