public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218336] mount(2) doesn't document ENOSPC when /proc/sys/fs/mount-max is exceeded
Date: Wed, 03 Jan 2024 16:04:08 +0000	[thread overview]
Message-ID: <bug-218336-11311-gnNgggM5qa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218336-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218336

--- Comment #1 from Simon McVittie (smcv@collabora.com) ---
The bubblewrap PR is https://github.com/containers/bubblewrap/pull/615.

The text I would hope to see in the man page could perhaps be something like:

**ENOSPC**
    The mount operation would cause the current mount namespace to
    have more mount points than allowed by _/proc/sys/fs/mount-max_.

...

**SEE ALSO**
    ...,
https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#mount-max

Or if the man-pages maintainers would prefer to have text that anticipates
potential future kernel changes, perhaps more generally:

**ENOSPC**
    The mount operation would cause a resource limit to be exceeded,
    for example more mount points than allowed by _/proc/sys/fs/mount-max_
    in the current mount namespace.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2024-01-03 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 15:32 [Bug 218336] New: mount(2) doesn't document ENOSPC when /proc/sys/fs/mount-max is exceeded bugzilla-daemon
2024-01-03 16:04 ` bugzilla-daemon [this message]
2024-01-03 16:29 ` [Bug 218336] " bugzilla-daemon

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=bug-218336-11311-gnNgggM5qa@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@vger.kernel.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