linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 2/2] statvfs.3: note f_favail = f_ffree on Linux
Date: Fri, 23 Jun 2023 23:00:08 +0200	[thread overview]
Message-ID: <3a449220b1a5b1d0be1749a98e5c284222072427.1687553930.git.nabijaczleweli@nabijaczleweli.xyz> (raw)
In-Reply-To: <a24c9d24-c131-5dcf-3089-353e2451a9e7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

It's unclear to me if inodes /may/ be reserved for root at all,
but the glibc comment in the Link would imply as much.

Link: https://lore.kernel.org/linux-man/f54kudgblgk643u32tb6at4cd3kkzha6hslahv24szs4raroaz@ogivjbfdaqtb/t/#u
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
---
 man3/statvfs.3 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/man3/statvfs.3 b/man3/statvfs.3
index b1f0e7545..23e4388fb 100644
--- a/man3/statvfs.3
+++ b/man3/statvfs.3
@@ -227,6 +227,12 @@ .SH NOTES
 .BR statvfs ()
 with the argument
 .IR path .
+.SH BUGS
+Under Linux,
+.I f_favail
+is always the same as
+.IR f_ffree ,
+even if some inodes are reserved for root.
 .SH STANDARDS
 POSIX.1-2008.
 .SH HISTORY
-- 
2.39.2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-06-23 21:00 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   ` наб [this message]
2023-06-24  0:39     ` [PATCH v2 2/2] statvfs.3: note f_favail = f_ffree on Linux наб
2023-07-05 13:57       ` Tom Schwindl
2023-07-08 17:11         ` Alejandro Colomar
2023-07-08 20:01           ` [PATCH v3 " наб
2023-07-15 13:41             ` 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=3a449220b1a5b1d0be1749a98e5c284222072427.1687553930.git.nabijaczleweli@nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=alx.manpages@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).