From: Alejandro Colomar <alx@kernel.org>
To: "Maja Kądziołka" <maya@compilercrim.es>
Cc: linux-man@vger.kernel.org, Kalesh Singh <kaleshsingh@google.com>
Subject: Re: [PATCH] man/man5/proc_pid_fdinfo.5: document the ino field
Date: Sat, 18 Jul 2026 14:03:57 +0200 [thread overview]
Message-ID: <altrcm5NL--VaUjl@devuan> (raw)
In-Reply-To: <7eeaa92f7a7cc14024a6474d4cc117e875185f6d.1784211190.git.maya@compilercrim.es>
[-- Attachment #1: Type: text/plain, Size: 3395 bytes --]
Hi Maja,
On 2026-07-16T16:51:07+0200, Maja Kądziołka wrote:
> Also expands the tabs into spaces where relevant, in order to ensure
> proper alignment between the fields when rendered by man.
>
> Signed-off-by: Maja Kądziołka <maya@compilercrim.es>
> Cc: Kalesh Singh <kaleshsingh@google.com>
Thanks! I've split the commit in two: documenting that these fields
(especially, mnt_id) are decimal deserves a separate commit, with its
own commit message.
Have a lovely day!
Alex
> ---
> man/man5/proc_pid_fdinfo.5 | 46 ++++++++++++++++++++++++--------------
> 1 file changed, 29 insertions(+), 17 deletions(-)
>
> diff --git a/man/man5/proc_pid_fdinfo.5 b/man/man5/proc_pid_fdinfo.5
> index 93c6cf269f31..f93b69c6c59d 100644
> --- a/man/man5/proc_pid_fdinfo.5
> +++ b/man/man5/proc_pid_fdinfo.5
> @@ -24,6 +24,7 @@ For regular files and directories, we see something like:
> pos: 1000
> flags: 01002002
> mnt_id: 21
> +ino: 63107
> .EE
> .in
> .P
> @@ -51,9 +52,14 @@ rather than the current setting of the close-on-exec flag.
> .I mnt_id
> This field, present since Linux 3.15,
> .\" commit 49d063cb353265c3af701bab215ac438ca7df36d
> -is the ID of the mount containing this file.
> +is the decimal ID of the mount containing this file.
> See the description of
> .IR /proc/ pid /mountinfo .
> +.TP
> +.I ino
> +This field, present since Linux 5.14,
> +.\" commit 3845f256a8b527127bfbd4ced21e93d9e89aa6d7
> +is the decimal inode number of the file.
> .P
> For eventfd file descriptors (see
> .BR eventfd (2)),
> @@ -63,9 +69,10 @@ the following fields:
> .P
> .in +4n
> .EX
> -pos: 0
> -flags: 02
> -mnt_id: 10
> +pos: 0
> +flags: 02
> +mnt_id: 10
> +ino: 63107
> eventfd\-count: 40
> .EE
> .in
> @@ -81,9 +88,10 @@ the following fields:
> .P
> .in +4n
> .EX
> -pos: 0
> -flags: 02
> -mnt_id: 10
> +pos: 0
> +flags: 02
> +mnt_id: 10
> +ino: 63107
> tfd: 9 events: 19 data: 74253d2500000009
> tfd: 7 events: 19 data: 74253d2500000007
> .EE
> @@ -114,10 +122,11 @@ the following fields:
> .P
> .in +4n
> .EX
> -pos: 0
> -flags: 02
> -mnt_id: 10
> -sigmask: 0000000000000006
> +pos: 0
> +flags: 02
> +mnt_id: 10
> +ino: 63107
> +sigmask: 0000000000000006
> .EE
> .in
> .P
> @@ -138,9 +147,10 @@ the following fields:
> .P
> .in +4n
> .EX
> -pos: 0
> -flags: 00
> -mnt_id: 11
> +pos: 0
> +flags: 00
> +mnt_id: 11
> +ino: 63107
> inotify wd:2 ino:7ef82a sdev:800001 mask:800afff ignored_mask:0 fhandle\-bytes:8 fhandle\-type:1 f_handle:2af87e00220ffd73
> inotify wd:1 ino:192627 sdev:800001 mask:800afff ignored_mask:0 fhandle\-bytes:8 fhandle\-type:1 f_handle:27261900802dfd73
> .EE
> @@ -176,9 +186,10 @@ the following fields:
> .P
> .in +4n
> .EX
> -pos: 0
> -flags: 02
> -mnt_id: 11
> +pos: 0
> +flags: 02
> +mnt_id: 11
> +ino: 63107
> fanotify flags:0 event\-flags:88002
> fanotify ino:19264f sdev:800001 mflags:0 mask:1 ignored_mask:0 fhandle\-bytes:8 fhandle\-type:1 f_handle:4f261900a82dfd73
> .EE
> @@ -232,6 +243,7 @@ the following fields:
> pos: 0
> flags: 02004002
> mnt_id: 13
> +ino: 63107
> clockid: 0
> ticks: 0
> settime flags: 03
> --
> 2.54.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-18 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 14:51 [PATCH] man/man5/proc_pid_fdinfo.5: document the ino field Maja Kądziołka
2026-07-18 12:03 ` 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=altrcm5NL--VaUjl@devuan \
--to=alx@kernel.org \
--cc=kaleshsingh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=maya@compilercrim.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.