From: Alejandro Colomar <alx@kernel.org>
To: Zeno Endemann <zeno.endemann@mailbox.org>
Cc: linux-man@vger.kernel.org
Subject: Re: Missing error values in ftruncate and fallocate man pages?
Date: Fri, 10 Apr 2026 19:47:48 +0200 [thread overview]
Message-ID: <adk2_jjPuyuQVbKI@debian> (raw)
In-Reply-To: <e53daaf2-3658-4645-ba29-fa488bec5ed8@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
Hi Zeno,
On 2026-04-10T18:52:29+0200, Zeno Endemann wrote:
> Hello,
>
> I noticed that the man page for truncate(2) does not list the error codes
> ENOSPC and EDQUOT, but I would think those should be potentially possible
> when actually expanding a file (may depend on file system?).
>
> Similarly, fallocate(2) also does not list EDQUOT (ENOSPC is there however).
> Finally, posix_fallocate(3) has no EDQUOT as well, and EIO also seems to be
> missing for this one.
>
> Or am I overlooking something?
Sounds plausible. If you could either perform some experiments or show
the relevant kernel sources that make it possible, we could know for
sure. If you find out it's possible, would you mind sending a patch?
Have a lovely day!
Alex
>
> Thanks,
> Zeno Endemann
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-04-10 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 16:52 Missing error values in ftruncate and fallocate man pages? Zeno Endemann
2026-04-10 17:47 ` Alejandro Colomar [this message]
2026-04-10 19:12 ` Zeno Endemann
2026-04-11 14:08 ` Alejandro Colomar
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=adk2_jjPuyuQVbKI@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=zeno.endemann@mailbox.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