> > I would feel much more comfortable if the two filesystems that expose > > these objects give us something like STATX_SUBVOLUME that userspace can > > raise in the request mask of statx(). > > Except that this doesn't fix any existing code. But why do we care? Current code already does need to know it is on a btrfs subvolume. They all know that btrfs subvolumes are special. They will need to know that btrfs subvolumes are special in the future even if they were vfsmounts. They would likely end up with another kind of confusion because suddenly vfsmounts have device numbers that aren't associated with the superblock that vfsmount belongs to. So nothing is really solved by vfsmounts either. The only thing that we achieved is that we somehow accommodated that st_dev hack. And that I consider nakable. > > > If userspace requests STATX_SUBVOLUME in the request mask, the two > > filesystems raise STATX_SUBVOLUME in the statx result mask and then also > > return the _real_ device number of the superblock and stop exposing that > > made up device number. > > What is a "real" device number? The device number of the superblock of the btrfs filesystem and not some made-up device number. I care about not making a btrfs specific problem the vfs's problem by hoisting that whole problem space a level up by mapping subvolumes to vfsmounts.
