[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpeguQAw+Mgc8QBNd+h3KV8=Y-SOGT7TB_N_54wa8MCoOSzg@mail.gmail.com>
Date: Fri, 3 Apr 2020 13:38:13 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Lennart Poettering <mzxreary@...inter.de>
Cc: Ian Kent <raven@...maw.net>, David Howells <dhowells@...hat.com>,
Christian Brauner <christian.brauner@...ntu.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>, dray@...hat.com,
Karel Zak <kzak@...hat.com>,
Miklos Szeredi <mszeredi@...hat.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Jeff Layton <jlayton@...hat.com>, andres@...razel.de,
keyrings@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, Aleksa Sarai <cyphar@...har.com>
Subject: Re: Upcoming: Notifications, FS notifications and fsinfo()
On Fri, Apr 3, 2020 at 1:11 PM Lennart Poettering <mzxreary@...inter.de> wrote:
>
> On Fr, 03.04.20 09:44, Ian Kent (raven@...maw.net) wrote:
>
> > > Currently the only way to find the mount id from a path is by parsing
> > > /proc/self/fdinfo/$fd. It is trivial, however, to extend statx(2) to
> > > return it directly from a path. Also the mount notification queue
> > > that David implemented contains the mount ID of the changed mount.
>
> I would love to have the mount ID exposed via statx().
Here's a patch.
Thanks,
Miklos
View attachment "statx-add-mount-id.patch" of type "text/x-patch" (2253 bytes)
Powered by blists - more mailing lists