Miklos Szeredi <miklos@xxxxxxxxxx> 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
