[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1576646.1596455376@warthog.procyon.org.uk>
Date: Mon, 03 Aug 2020 12:49:36 +0100
From: David Howells <dhowells@...hat.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: dhowells@...hat.com, Ian Kent <raven@...maw.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Casey Schaufler <casey@...aufler-ca.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Christian Brauner <christian@...uner.io>, andres@...razel.de,
Jeff Layton <jlayton@...hat.com>, dray@...hat.com,
Karel Zak <kzak@...hat.com>, keyrings@...r.kernel.org,
Linux API <linux-api@...r.kernel.org>,
linux-fsdevel@...r.kernel.org,
LSM <linux-security-module@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/17] watch_queue: Implement mount topology and attribute change notifications [ver #5]
Miklos Szeredi <miklos@...redi.hu> wrote:
> OTOH mount notification is way smaller and IMO a more mature
> interface. So just picking the unique ID patch into this set might
> make sense.
But userspace can't retrieve the unique ID without fsinfo() as things stand.
I'm changing it so that the fields are 64-bit, but initialised with the
existing mount ID in the notifications set. The fsinfo set changes that to a
unique ID. I'm tempted to make the unique IDs start at UINT_MAX+1 to
disambiguate them.
David
Powered by blists - more mailing lists