[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvyegY-p6MWCBZADRYjrxH17P+EEajupYYojqRkfkoNM3w@mail.gmail.com>
Date: Fri, 3 Apr 2020 14:05:23 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Lennart Poettering <mzxreary@...inter.de>,
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 <linux-fsdevel@...r.kernel.org>,
LKML <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:40 PM Miklos Szeredi <miklos@...redi.hu> wrote:
>
> 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.
I was looking more than once for a nice way to get the mount id.
Having it exposed via statx() would be great!
--
Thanks,
//richard
Powered by blists - more mailing lists