From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>, Karel Zak <kzak@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Ian Kent <raven@themaw.net>,
Josef Bacik <josef@toxicpanda.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v3 0/2] fs: allow statmount to fetch the subtype and devname
Date: Mon, 11 Nov 2024 08:42:26 -0500 [thread overview]
Message-ID: <5418c22b64ac0d8d469d8f9725f1b7685e8daa1b.camel@kernel.org> (raw)
In-Reply-To: <20241111-ruhezeit-renovieren-d78a10af973f@brauner>
On Mon, 2024-11-11 at 10:17 +0100, Christian Brauner wrote:
> On Thu, 07 Nov 2024 16:00:05 -0500, Jeff Layton wrote:
> > Meta has some internal logging that scrapes /proc/self/mountinfo today.
> > I'd like to convert it to use listmount()/statmount(), so we can do a
> > better job of monitoring with containers. We're missing some fields
> > though. This patchset adds them.
> >
> >
>
> I know Karel has been wanting this for libmount as well. Thanks for
> doing this! It would be nice if you could also add some selftests!
>
(cc'ing Karel)
Thanks. We may need to tweak this a bit, based on Miklos' comments
about how empty strings are handled now, but it shouldn't be too big a
change.
I actually have a related question about libmount: glibc doesn't
currently provide syscall wrappers for statmount() and listmount().
Would it make sense to have libmount provide those? We could copy the
wrappers in tools/testing/selftests/filesystems/statmount/statmount.h
to libmount.h.
It's error-prone and a pain to roll these yourself, and that would make
things simpler until someone is ready to do something for glibc.
Another idea might be to start a new userland header file that is just
a collection of static inline wrappers for syscalls that aren't
packaged in glibc.e.g. pidfd_open also doesn't have glibc bindings, so
we could add that there too.
> ---
>
> Applied to the vfs.misc branch of the vfs/vfs.git tree.
> Patches in the vfs.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs.misc
>
> [1/2] fs: add the ability for statmount() to report the fs_subtype
> https://git.kernel.org/vfs/vfs/c/ddfdeccd46bd
> [2/2] fs: add the ability for statmount() to report the mnt_devname
> https://git.kernel.org/vfs/vfs/c/6fb42b3c00cd
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-11-11 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 21:00 Jeff Layton
2024-11-07 21:00 ` [PATCH v3 1/2] fs: add the ability for statmount() to report the fs_subtype Jeff Layton
2024-11-11 10:49 ` Miklos Szeredi
2024-11-11 11:28 ` Jeff Layton
2024-11-11 13:01 ` Miklos Szeredi
2024-11-11 13:28 ` Jeff Layton
2024-11-11 13:30 ` Christian Brauner
2024-11-07 21:00 ` [PATCH v3 2/2] fs: add the ability for statmount() to report the mnt_devname Jeff Layton
2024-11-08 12:19 ` Jan Kara
2024-11-11 14:31 ` Miklos Szeredi
2024-11-11 9:17 ` [PATCH v3 0/2] fs: allow statmount to fetch the subtype and devname Christian Brauner
2024-11-11 13:42 ` Jeff Layton [this message]
2024-11-12 9:37 ` Karel Zak
2024-11-12 9:42 ` Christian Brauner
2024-11-12 10:24 ` Miklos Szeredi
2024-11-12 13:12 ` Christian Brauner
2024-11-12 11:33 ` Jeff Layton
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=5418c22b64ac0d8d469d8f9725f1b7685e8daa1b.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--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®