From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Tom Schwindl <schwindl@posteo.de>
Subject: [PATCH v3 2/2] statvfs.3: note f_favail = f_ffree on Linux
Date: Sat, 8 Jul 2023 22:01:29 +0200 [thread overview]
Message-ID: <rubximyg43zxy2itklr6jrk3bisxt52zbsbwfdovpy7b5cgma7@zwl7wl5xnpzz> (raw)
In-Reply-To: <c79b5d7e-540a-ce0a-2ee7-ce5fdde6947c@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Quoting myself from #musl:
01:59:40 hm, I think this was just invented for symmetry with bfree/bavail
02:00:46 FFS has minfree for space but nothing equivalent for inodes
02:32:31 (this is mirrored in ext4;
a global grep over DragonFlyBSD and the illumos gate
showed just NFSv3 forwarding from the server;
OpenBSD always sets it to the same thing as f_ffree;
oddly, NetBSD /does/ calculate it differently
for LFS and FFS but due to queued writes or
w/e not because of root reservation;
and as expected a lot of "/* what to put in here? */"
and "// XXX same??")
Link: https://lore.kernel.org/linux-man/f54kudgblgk643u32tb6at4cd3kkzha6hslahv24szs4raroaz@ogivjbfdaqtb/t/#u
Cc: Tom Schwindl <schwindl@posteo.de>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
---
man3/statvfs.3 | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/man3/statvfs.3 b/man3/statvfs.3
index b1f0e7545..50b568ab1 100644
--- a/man3/statvfs.3
+++ b/man3/statvfs.3
@@ -227,6 +227,14 @@ .SH NOTES
.BR statvfs ()
with the argument
.IR path .
+.PP
+Under Linux,
+.I f_favail
+is always the same as
+.IR f_ffree ,
+and there's no way for a filesystem to report otherwise.
+This is not an issue, since no filesystems with an inode
+root reservation exist.
.SH STANDARDS
POSIX.1-2008.
.SH HISTORY
--
2.39.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-08 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 19:58 [f]statfs(2) shaded as deprecated? наб
2023-06-23 20:08 ` Alejandro Colomar
2023-06-23 21:00 ` [PATCH 1/2] statfs.2: unshade as deprecated, but direct to statvfs(3) наб
2023-06-23 21:00 ` [PATCH 2/2] statvfs.3: note f_favail = f_ffree on Linux наб
2023-06-24 0:39 ` [PATCH v2 " наб
2023-07-05 13:57 ` Tom Schwindl
2023-07-08 17:11 ` Alejandro Colomar
2023-07-08 20:01 ` наб [this message]
2023-07-15 13:41 ` [PATCH v3 " Alejandro Colomar
2023-07-18 11:43 ` [PATCH v2 " Alejandro Colomar
2023-07-18 11:48 ` 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=rubximyg43zxy2itklr6jrk3bisxt52zbsbwfdovpy7b5cgma7@zwl7wl5xnpzz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=schwindl@posteo.de \
/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 NNTP newsgroup(s).