[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200403154139.GA34867@gardel-login>
Date: Fri, 3 Apr 2020 17:41:39 +0200
From: Lennart Poettering <mzxreary@...inter.de>
To: David Howells <dhowells@...hat.com>
Cc: Miklos Szeredi <miklos@...redi.hu>, Ian Kent <raven@...maw.net>,
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 Fr, 03.04.20 16:36, David Howells (dhowells@...hat.com) wrote:
> Lennart Poettering <mzxreary@...inter.de> wrote:
>
> > BTW, while we are at it: one more thing I'd love to see exposed by
> > statx() is a simple flag whether the inode is a mount point.
>
> Note that an inode or a dentry might be a mount point in one namespace, but
> not in another. Do you actually mean an inode - or do you actually mean the
> (mount,dentry) pair that you're looking at? (Ie. should it be namespace
> specific?)
yes, it should be specific to the mount hierarchy in the current namespace.
Lennart
--
Lennart Poettering, Berlin
Powered by blists - more mailing lists