[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2325155.1596645852@warthog.procyon.org.uk>
Date: Wed, 05 Aug 2020 17:44:12 +0100
From: David Howells <dhowells@...hat.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: dhowells@...hat.com, viro@...iv.linux.org.uk,
torvalds@...ux-foundation.org, raven@...maw.net,
mszeredi@...hat.com, christian@...uner.io, jannh@...gle.com,
darrick.wong@...cle.com, kzak@...hat.com, jlayton@...hat.com,
linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 15/18] fsinfo: Add an attribute that lists all the visible mounts in a namespace [ver #21]
Miklos Szeredi <miklos@...redi.hu> wrote:
> > where each element contains a once-in-a-system-lifetime unique ID, the
> > mount ID (which may get reused), the parent mount ID and sums of the
> > notification/change counters for the mount and its superblock.
>
> The change counters are currently conditional on CONFIG_MOUNT_NOTIFICATIONS.
> Is this is intentional?
Yeah - the counters aren't driven unless CONFIG_MOUNT_NOTIFICATIONS=y.
I could perhaps make it so they're driven in both cases, but driving the
in-subtree counter is somewhat tied up in the notification posting.
This is something that can be fixed after this patchset is taken - if it is
taken since that doesn't change the UAPI.
David
Powered by blists - more mailing lists