From: "Darrick J. Wong" <djwong@kernel.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, "Pali Rohár" <pali@kernel.org>,
"Jan Kara" <jack@suse.cz>,
"G. Branden Robinson" <branden@debian.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] man/man3/readdir.3, man/man3type/stat.3type: Improve documentation about .d_ino and .st_ino
Date: Fri, 31 Oct 2025 08:25:31 -0700 [thread overview]
Message-ID: <20251031152531.GP6174@frogsfrogsfrogs> (raw)
In-Reply-To: <bfa7e72ea17ed369a1cf7589675c35728bb53ae4.1761907223.git.alx@kernel.org>
On Fri, Oct 31, 2025 at 11:44:14AM +0100, Alejandro Colomar wrote:
> Suggested-by: Pali Rohár <pali@kernel.org>
> Co-authored-by: Pali Rohár <pali@kernel.org>
> Co-authored-by: Jan Kara <jack@suse.cz>
> Cc: "G. Branden Robinson" <branden@debian.org>
> Cc: <linux-fsdevel@vger.kernel.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
>
> Hi Jan,
>
> I've put your suggestions into the patch. I've also removed the
> sentence about POSIX, as Pali discussed with Branden.
>
> At the bottom of the email is the range-diff against the previous
> version.
>
>
> Have a lovely day!
> Alex
>
> man/man3/readdir.3 | 19 ++++++++++++++++++-
> man/man3type/stat.3type | 20 +++++++++++++++++++-
> 2 files changed, 37 insertions(+), 2 deletions(-)
>
> diff --git a/man/man3/readdir.3 b/man/man3/readdir.3
> index e1c7d2a6a..220643795 100644
> --- a/man/man3/readdir.3
> +++ b/man/man3/readdir.3
> @@ -58,7 +58,24 @@ .SH DESCRIPTION
> structure are as follows:
> .TP
> .I .d_ino
> -This is the inode number of the file.
> +This is the inode number of the file
> +in the filesystem containing
> +the directory on which
> +.BR readdir ()
> +was called.
> +If the directory entry is the mount point,
nitpicking english:
"...is a mount point," ?
--D
> +then
> +.I .d_ino
> +differs from
> +.I .st_ino
> +returned by
> +.BR stat (2)
> +on this file:
> +.I .d_ino
> +is the inode number of the mount point,
> +while
> +.I .st_ino
> +is the inode number of the root directory of the mounted filesystem.
> .TP
> .I .d_off
> The value returned in
> diff --git a/man/man3type/stat.3type b/man/man3type/stat.3type
> index 76ee3765d..ea9acc5ec 100644
> --- a/man/man3type/stat.3type
> +++ b/man/man3type/stat.3type
> @@ -66,7 +66,25 @@ .SH DESCRIPTION
> macros may be useful to decompose the device ID in this field.)
> .TP
> .I .st_ino
> -This field contains the file's inode number.
> +This field contains the file's inode number
> +in the filesystem on
> +.IR .st_dev .
> +If
> +.BR stat (2)
> +was called on the mount point,
> +then
> +.I .st_ino
> +differs from
> +.I .d_ino
> +returned by
> +.BR readdir (3)
> +for the corresponding directory entry in the parent directory.
> +In this case,
> +.I .st_ino
> +is the inode number of the root directory of the mounted filesystem,
> +while
> +.I .d_ino
> +is the inode number of the mount point in the parent filesystem.
> .TP
> .I .st_mode
> This field contains the file type and mode.
>
> Range-diff against v2:
> 1: d3eeebe81 ! 1: bfa7e72ea man/man3/readdir.3, man/man3type/stat.3type: Improve documentation about .d_ino and .st_ino
> @@ Commit message
>
> Suggested-by: Pali Rohár <pali@kernel.org>
> Co-authored-by: Pali Rohár <pali@kernel.org>
> + Co-authored-by: Jan Kara <jack@suse.cz>
> Cc: "G. Branden Robinson" <branden@debian.org>
> Cc: <linux-fsdevel@vger.kernel.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> @@ man/man3/readdir.3: .SH DESCRIPTION
> .TP
> .I .d_ino
> -This is the inode number of the file.
> -+This is the inode number of the file,
> -+which belongs to the filesystem
> -+.I .st_dev
> -+(see
> -+.BR stat (3type))
> -+of the directory on which
> ++This is the inode number of the file
> ++in the filesystem containing
> ++the directory on which
> +.BR readdir ()
> +was called.
> +If the directory entry is the mount point,
> +then
> +.I .d_ino
> +differs from
> -+.IR .st_ino :
> ++.I .st_ino
> ++returned by
> ++.BR stat (2)
> ++on this file:
> +.I .d_ino
> -+is the inode number of the underlying mount point,
> ++is the inode number of the mount point,
> +while
> +.I .st_ino
> -+is the inode number of the mounted file system.
> -+According to POSIX,
> -+this Linux behavior is considered to be a bug,
> -+but is nevertheless conforming.
> ++is the inode number of the root directory of the mounted filesystem.
> .TP
> .I .d_off
> The value returned in
> @@ man/man3type/stat.3type: .SH DESCRIPTION
> .TP
> .I .st_ino
> -This field contains the file's inode number.
> -+This field contains the file's inode number,
> -+which belongs to the
> ++This field contains the file's inode number
> ++in the filesystem on
> +.IR .st_dev .
> +If
> +.BR stat (2)
> +was called on the mount point,
> +then
> -+.I .d_ino
> -+differs from
> -+.IR .st_ino :
> -+.I .d_ino
> -+is the inode number of the underlying mount point,
> -+while
> +.I .st_ino
> -+is the inode number of the mounted file system.
> ++differs from
> ++.I .d_ino
> ++returned by
> ++.BR readdir (3)
> ++for the corresponding directory entry in the parent directory.
> ++In this case,
> ++.I .st_ino
> ++is the inode number of the root directory of the mounted filesystem,
> ++while
> ++.I .d_ino
> ++is the inode number of the mount point in the parent filesystem.
> .TP
> .I .st_mode
> This field contains the file type and mode.
>
> base-commit: f305f7647d5cf62e7e764fb7a25c4926160c594f
> --
> 2.51.0
>
>
next prev parent reply other threads:[~2025-10-31 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250525103344.fe27ugiytfyoadz5@pali>
[not found] ` <juxbjjsnt5mvtyctd72fcnc4o2u5wamqz7yd5occuor4clzkhx@zvob6krj6sq3>
[not found] ` <20250528182519.l6kyy5ebiivev2u5@pali>
[not found] ` <m5drckhk4mkw3l6fzfqyelobscbrmx6jefpjik4nj4j5ala7ff@mrm6ds7a4lk2>
[not found] ` <20250528194105.dqc2bgfck6n3xfya@pali>
2025-05-28 19:59 ` Improving inode number documentation Alejandro Colomar
2025-05-28 21:31 ` [RFC v1] man/man3/readdir.3, man/man3type/stat.3type: Improve documentation about .d_ino and .st_ino Alejandro Colomar
2025-05-28 22:54 ` G. Branden Robinson
2025-10-31 10:44 ` [PATCH v3] " Alejandro Colomar
2025-10-31 10:56 ` Jan Kara
2025-10-31 11:31 ` Alejandro Colomar
2025-10-31 17:10 ` Pali Rohár
2025-10-31 15:25 ` Darrick J. Wong [this message]
2025-11-02 21:17 ` Alejandro Colomar
2025-11-03 11:28 ` Jan Kara
2025-11-09 12:07 ` 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=20251031152531.GP6174@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=alx@kernel.org \
--cc=branden@debian.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=pali@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).