From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH man-pages] statx.2: Add STATX_MNT_ID
Date: Fri, 13 Aug 2021 01:13:20 +0200 [thread overview]
Message-ID: <cdb757b8-b3e5-b951-8c3d-44ac20f18558@gmail.com> (raw)
In-Reply-To: <162880868648.15074.7283929646453264436@noble.neil.brown.name>
Hello Neil,
On 8/13/21 12:46 AM, NeilBrown wrote:
>
> Linux 5.8 adds STATX_MNT_ID and stx_mnt_id.
> Add description to statx.2
>
> Signed-off-by: NeilBrown <neilb@suse.de>
Thanks. Patch applied.
Cheers,
Michael
> ---
> man2/statx.2 | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/man2/statx.2 b/man2/statx.2
> index 9e3aeaa36fa3..c41ee45f9bc4 100644
> --- a/man2/statx.2
> +++ b/man2/statx.2
> @@ -77,6 +77,7 @@ struct statx {
> containing the filesystem where the file resides */
> __u32 stx_dev_major; /* Major ID */
> __u32 stx_dev_minor; /* Minor ID */
> + __u64 stx_mnt_id; /* Mount ID */
> };
> .EE
> .in
> @@ -258,6 +259,7 @@ STATX_SIZE Want stx_size
> STATX_BLOCKS Want stx_blocks
> STATX_BASIC_STATS [All of the above]
> STATX_BTIME Want stx_btime
> +STATX_MNT_ID Want stx_mnt_id (since Linux 5.8)
> STATX_ALL [All currently available fields]
> .TE
> .in
> @@ -411,6 +413,13 @@ The device on which this file (inode) resides.
> .IR stx_rdev_major " and " stx_rdev_minor
> The device that this file (inode) represents if the file is of block or
> character device type.
> +.TP
> +.I stx_mnt_id
> +.\" commit fa2fcf4f1df1559a0a4ee0f46915b496cc2ebf60
> +The mount ID of the mount containing the file. This is the same number reported by
> +.BR name_to_handle_at (2)
> +and corresponds to the number in the first field in one of the records in
> +.IR /proc/self/mountinfo .
> .PP
> For further information on the above fields, see
> .BR inode (7).
> @@ -573,9 +582,11 @@ is Linux-specific.
> .BR access (2),
> .BR chmod (2),
> .BR chown (2),
> +.BR name_to_handle_at (2),
> .BR readlink (2),
> .BR stat (2),
> .BR utime (2),
> +.BR proc (5),
> .BR capabilities (7),
> .BR inode (7),
> .BR symlink (7)
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-08-12 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 22:46 [PATCH man-pages] statx.2: Add STATX_MNT_ID NeilBrown
2021-08-12 23:13 ` Michael Kerrisk (man-pages) [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=cdb757b8-b3e5-b951-8c3d-44ac20f18558@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=neilb@suse.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).