On Mon 23-06-25 11:01:29, Christian Brauner wrote: > Allow a filesystem to indicate that it supports encoding autonomous file > handles that can be decoded without having to pass a filesystem for the > filesystem. In other words, the file handle uniquely identifies the > filesystem. > > Signed-off-by: Christian Brauner <brauner@xxxxxxxxxx> ... > diff --git a/include/linux/exportfs.h b/include/linux/exportfs.h > index 45b38a29643f..959a1f7d46d0 100644 > --- a/include/linux/exportfs.h > +++ b/include/linux/exportfs.h > @@ -194,7 +194,8 @@ struct handle_to_path_ctx { > /* Flags supported in encoded handle_type that is exported to user */ > #define FILEID_IS_CONNECTABLE 0x10000 > #define FILEID_IS_DIR 0x20000 > -#define FILEID_VALID_USER_FLAGS (FILEID_IS_CONNECTABLE | FILEID_IS_DIR) > +#define FILEID_IS_AUTONOMOUS 0x40000 > +#define FILEID_VALID_USER_FLAGS (FILEID_IS_CONNECTABLE | FILEID_IS_DIR | FILEID_IS_AUTONOMOUS) Is there a reason for FILEID_IS_AUTONOMOUS? As far as I understand the fh_type has to encode filesystem type anyway so that you know which root to pick. So FILEID_IS_AUTONOMOUS is just duplicating the information? But maybe there's some benefit in having FILEID_IS_AUTONOMOUS which I'm missing... Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR