From: Alejandro Colomar <alx@kernel.org>
To: "Priedhorsky, Reid" <reidpr@lanl.gov>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: mount(2) missing EOVERFLOW
Date: Fri, 22 Dec 2023 18:26:55 +0100 [thread overview]
Message-ID: <ZYXG34n78pvXXyG0@debian> (raw)
In-Reply-To: <A1B87125-51E7-498B-B362-502616EBED08@lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Hello Reid, Eric,
On Fri, Dec 01, 2023 at 05:52:05PM +0000, Priedhorsky, Reid wrote:
> Looks like mount(2) can fail with EOVERFLOW [1], but this is not documented in the mount(2) man page [2,3].
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=183461
From this link, I see the original report was for mkdir(2). So it's not
just mount(2).
Eric, which pages need to document EOVERFLOW?
Have a lovely day,
Alex
> [2]: https://www.man7.org/linux/man-pages/man2/mount.2.html
> [3]: https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man2/mount.2
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-12-22 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 17:52 mount(2) missing EOVERFLOW Priedhorsky, Reid
2023-12-22 17:26 ` 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=ZYXG34n78pvXXyG0@debian \
--to=alx@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-man@vger.kernel.org \
--cc=reidpr@lanl.gov \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).