public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: me@black-desk.cn
Cc: linux-man@vger.kernel.org, CAI Qian <caiqian@redhat.com>,
	 "Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] man/man2/mount.2: add ENOSPC
Date: Fri, 30 Jan 2026 14:07:57 +0100	[thread overview]
Message-ID: <aXyssOLaZl8qkSZ1@devuan> (raw)
In-Reply-To: <20260130-add-enospc-for-mount-v1-1-85b45f0ce3d8@black-desk.cn>

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

[CC += CAI, Eric]

Hi Chen,

On 2026-01-30T16:13:54+0800, Chen Linxuan via B4 Relay wrote:
> From: Chen Linxuan <me@black-desk.cn>
> 
> After linux commit d29216842a85 ("mnt: Add a per mount namespace limit
> on the number of mounts"), mount(2) might return ENOSPC.
> 
> ---
> Signed-off-by: Chen Linxuan <me@black-desk.cn>

The sign-off should be in the commit message (above the '---').

> ---
>  man/man2/mount.2 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man/man2/mount.2 b/man/man2/mount.2
> index d5a68cb836b2..bebd3c1792ba 100644
> --- a/man/man2/mount.2
> +++ b/man/man2/mount.2
> @@ -793,6 +793,19 @@ A pathname was empty or had a nonexistent component.
>  .B ENOMEM
>  The kernel could not allocate a free page to copy filenames or data into.
>  .TP
> +.B ENOSPC
> +Number of mounts will exceed the limit after this syscall in some mount
> +namespaces. This limit is controlled by

Please use semantic newlines.  See man-pages(7):

$ MANWIDTH=72 man man-pages | awk '/Use semantic newlines/,/^$/'
   Use semantic newlines
     In the source of a manual page, new sentences should be started on
     new lines, long sentences should be split  into  lines  at  clause
     breaks  (commas,  semicolons, colons, and so on), and long clauses
     should be split at phrase boundaries.  This convention,  sometimes
     known as "semantic newlines", makes it easier to see the effect of
     patches, which often operate at the level of individual sentences,
     clauses, or phrases.


Have a lovely day!
Alex

> +.IR /proc/sys/fs/mount-max ,
> +see
> +.BR proc_sys_fs (5)
> +for details of this limit.
> +Note that this limit applies both to the mount namespace where the mount
> +operation occurs and to any mount namespaces to which the mount will propagate.
> +See
> +.BR mount_namespaces (7)
> +for details for mount namespace and mount propagation.
> +.TP
>  .B ENOTBLK
>  .I source
>  is not a block device (and a device was required).
> 
> ---
> base-commit: 6754bd1a126ed1e9b7d9c2bc1d221681f5182bb3
> change-id: 20260130-add-enospc-for-mount-3ea1e87af6ee
> 
> Best regards,
> -- 
> Chen Linxuan <me@black-desk.cn>
> 
> 
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-01-30 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  8:13 [PATCH] man/man2/mount.2: add ENOSPC Chen Linxuan via B4 Relay
2026-01-30 13:07 ` 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=aXyssOLaZl8qkSZ1@devuan \
    --to=alx@kernel.org \
    --cc=caiqian@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-man@vger.kernel.org \
    --cc=me@black-desk.cn \
    /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