tree 6c5a191bbe510de44fad602a0f3d112c677f2e4d
parent 7b54e2c4c5402b035b84d8097c1a7c082dc9a79b
author Christian Brauner <christian.brauner@ubuntu.com> 1626693051 +0200
committer Christian Brauner <christian.brauner@ubuntu.com> 1627291981 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iHUEABYKAB0WIQRAhzRXHqcMeLMyaSiRxhvAZXjcogUCYP6BTQAKCRCRxhvAZXjc
 onEWAQC5zWT+uBhkHC7T3wMWbo02/uPdoo9DrG4SSTT3zEEbSwEAmtk3UYIQMrJD
 sgtw1S7vBX5zh4XG+vBY90tXGL5Rawg=
 =hHeV
 -----END PGP SIGNATURE-----

btrfs/super: allow idmapped btrfs

Now that we converted btrfs internally to account for idmapped mounts allow the
creation of idmapped mounts on btrfs by setting the FS_ALLOW_IDMAP flag.  We
only need to raise this flag on the btrfs_root_fs_type filesystem since
btrfs_mount_root() is ultimately responsible for allocating the superblock and
is called into from btrfs_mount() associated with btrfs_fs_type.

The conversion of the btrfs inode operations was straightforward. Regarding
btrfs specific ioctls that perform checks based on inode permissions only those
have been allowed that are not filesystem wide operations and hence can be
reasonably charged against a specific mount.

Cc: Chris Mason <clm@fb.com>
Cc: Josef Bacik <josef@toxicpanda.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>