tree f6844515562c03b781c59e0c53356c924681db5b
parent d286e1f24d1f1bafecc727544c3500a33b8a5697
author Christian Brauner <christian.brauner@ubuntu.com> 1625213244 +0200
committer Christian Brauner <christian.brauner@ubuntu.com> 1627292578 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iHUEABYKAB0WIQRAhzRXHqcMeLMyaSiRxhvAZXjcogUCYP6DpgAKCRCRxhvAZXjc
 olRjAQC8TciuNSN2dOn2t4sDLCzfPWBEDwfu9PPe001YS3Su+wD+OB6Oe5SPJEEu
 9yVaWEbF6PyTQjSvz6Imv2CzMCB34gc=
 =Eqz1
 -----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>
---
/* v2 */
unchanged

/* v3 */
unchanged