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 v2] man/man2/mount.2: add ENOSPC
Date: Wed, 11 Feb 2026 00:19:17 +0100 [thread overview]
Message-ID: <aYu845Smj2aepWud@devuan> (raw)
In-Reply-To: <20260201-add-enospc-for-mount-v2-1-43c990199cc6@black-desk.cn>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
Hi Chen,
On 2026-02-01T11:59:33+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>
Thanks! I've applied the patch.
Have a lovely night!
Alex
> ---
> Changes in v2:
> - Apply changes suggested by Alejandro:
> - Correct the sign-off line;
> - Use semantic newlines.
> - Link to v1: https://lore.kernel.org/r/20260130-add-enospc-for-mount-v1-1-85b45f0ce3d8@black-desk.cn
> ---
> man/man2/mount.2 | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/man/man2/mount.2 b/man/man2/mount.2
> index d5a68cb836b2..35fef946a6d6 100644
> --- a/man/man2/mount.2
> +++ b/man/man2/mount.2
> @@ -793,6 +793,21 @@ 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
> +.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 --]
prev parent reply other threads:[~2026-02-10 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 3:59 [PATCH v2] man/man2/mount.2: add ENOSPC Chen Linxuan via B4 Relay
2026-02-10 23:19 ` 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=aYu845Smj2aepWud@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