Miklos Szeredi <[email protected]> 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
