From: Jan Kara <jack@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Josef Bacik <josef@toxicpanda.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: add the ability for statmount() to report the fs_subtype
Date: Wed, 6 Nov 2024 14:37:15 +0100 [thread overview]
Message-ID: <20241106133715.ellv3pf7ekz34fmi@quack3> (raw)
In-Reply-To: <20241106-statmount-v1-1-b93bafd97621@kernel.org>
On Wed 06-11-24 08:29:19, Jeff Layton wrote:
> /proc/self/mountinfo prints out the sb->s_subtype after the type. In
> particular, FUSE makes use of this to display the fstype as
> fuse.<subtype>.
>
> Add STATMOUNT_FS_SUBTYPE and claim one of the __spare2 fields to point
> to the offset into the str[] array. The STATMOUNT_FS_SUBTYPE will only
> be set in the return mask if there is a subtype associated with the
> mount.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Looks good to me. I'm just curious: Do you have any particular user that is
interested in getting subtype from statmount(2)?
Honza
> ---
> fs/namespace.c | 20 +++++++++++++++++++-
> include/uapi/linux/mount.h | 5 ++++-
> 2 files changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index ba77ce1c6788dfe461814b5826fcbb3aab68fad4..5f2fb692449a9c0a15b60549fb9f7bedd10f1f3d 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -5006,6 +5006,14 @@ static int statmount_fs_type(struct kstatmount *s, struct seq_file *seq)
> return 0;
> }
>
> +static int statmount_fs_subtype(struct kstatmount *s, struct seq_file *seq)
> +{
> + struct super_block *sb = s->mnt->mnt_sb;
> +
> + seq_puts(seq, sb->s_subtype);
> + return 0;
> +}
> +
> static void statmount_mnt_ns_id(struct kstatmount *s, struct mnt_namespace *ns)
> {
> s->sm.mask |= STATMOUNT_MNT_NS_ID;
> @@ -5064,6 +5072,13 @@ static int statmount_string(struct kstatmount *s, u64 flag)
> sm->mnt_opts = seq->count;
> ret = statmount_mnt_opts(s, seq);
> break;
> + case STATMOUNT_FS_SUBTYPE:
> + /* ignore if no s_subtype */
> + if (!s->mnt->mnt_sb->s_subtype)
> + return 0;
> + sm->fs_subtype = seq->count;
> + ret = statmount_fs_subtype(s, seq);
> + break;
> default:
> WARN_ON_ONCE(true);
> return -EINVAL;
> @@ -5203,6 +5218,9 @@ static int do_statmount(struct kstatmount *s, u64 mnt_id, u64 mnt_ns_id,
> if (!err && s->mask & STATMOUNT_MNT_OPTS)
> err = statmount_string(s, STATMOUNT_MNT_OPTS);
>
> + if (!err && s->mask & STATMOUNT_FS_SUBTYPE)
> + err = statmount_string(s, STATMOUNT_FS_SUBTYPE);
> +
> if (!err && s->mask & STATMOUNT_MNT_NS_ID)
> statmount_mnt_ns_id(s, ns);
>
> @@ -5224,7 +5242,7 @@ static inline bool retry_statmount(const long ret, size_t *seq_size)
> }
>
> #define STATMOUNT_STRING_REQ (STATMOUNT_MNT_ROOT | STATMOUNT_MNT_POINT | \
> - STATMOUNT_FS_TYPE | STATMOUNT_MNT_OPTS)
> + STATMOUNT_FS_TYPE | STATMOUNT_MNT_OPTS | STATMOUNT_FS_SUBTYPE)
>
> static int prepare_kstatmount(struct kstatmount *ks, struct mnt_id_req *kreq,
> struct statmount __user *buf, size_t bufsize,
> diff --git a/include/uapi/linux/mount.h b/include/uapi/linux/mount.h
> index 225bc366ffcbf0319929e2f55f1fbea88e4d7b81..fa206fb56b3b25cf80f7d430e1b6bab19c3220e4 100644
> --- a/include/uapi/linux/mount.h
> +++ b/include/uapi/linux/mount.h
> @@ -173,7 +173,9 @@ struct statmount {
> __u32 mnt_root; /* [str] Root of mount relative to root of fs */
> __u32 mnt_point; /* [str] Mountpoint relative to current root */
> __u64 mnt_ns_id; /* ID of the mount namespace */
> - __u64 __spare2[49];
> + __u32 fs_subtype; /* [str] Subtype of fs_type (if any) */
> + __u32 __spare1[1];
> + __u64 __spare2[48];
> char str[]; /* Variable size part containing strings */
> };
>
> @@ -207,6 +209,7 @@ struct mnt_id_req {
> #define STATMOUNT_FS_TYPE 0x00000020U /* Want/got fs_type */
> #define STATMOUNT_MNT_NS_ID 0x00000040U /* Want/got mnt_ns_id */
> #define STATMOUNT_MNT_OPTS 0x00000080U /* Want/got mnt_opts */
> +#define STATMOUNT_FS_SUBTYPE 0x00000100U /* Want/got subtype */
>
> /*
> * Special @mnt_id values that can be passed to listmount
>
> ---
> base-commit: 26213e1a6caa5a7f508b919059b0122b451f4dfe
> change-id: 20241106-statmount-3f91a7ed75fa
>
> Best regards,
> --
> Jeff Layton <jlayton@kernel.org>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-11-06 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 13:29 Jeff Layton
2024-11-06 13:37 ` Jan Kara [this message]
2024-11-06 13:56 ` Jeff Layton
2024-11-06 16:39 ` Jan Kara
2024-11-06 23:07 ` Ian Kent
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=20241106133715.ellv3pf7ekz34fmi@quack3 \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®