[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 5 May 2022 15:59:45 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Karel Zak <kzak@...hat.com>
Cc: linux-fsdevel@...r.kernel.org, Dave Chinner <david@...morbit.com>,
"Theodore Ts'o" <tytso@....edu>,
Greg KH <gregkh@...uxfoundation.org>,
Christian Brauner <brauner@...nel.org>,
linux-kernel@...r.kernel.org,
Linux API <linux-api@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>,
LSM <linux-security-module@...r.kernel.org>,
Ian Kent <raven@...maw.net>,
David Howells <dhowells@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Christian Brauner <christian@...uner.io>,
Amir Goldstein <amir73il@...il.com>,
James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [RFC PATCH] getting misc stats/attributes via xattr API
On Thu, 5 May 2022 at 14:30, Karel Zak <kzak@...hat.com> wrote:
> Is there a way how to get mountinfo-like entry by mount ID for some
> sub-tree? Something like:
>
> getfattr -etext -n ":mnt:info:21" /
Yes:
getfattr -etext -n ":mntns:21:info" /
>
> The interface has to be consistent with some notification system (I
> see your question about fsnotify/fanotify at linux-fsdevel) and mount
> ID seems better than paths due to over-mounts, etc.
Right.
If the mount notification doesn't fit into fsnotify well, the original
patch from David could be used. I think that part was
uncontroversial.
Thanks,
Miklos
Powered by blists - more mailing lists