btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls
authorJeff Mahoney <jeffm@suse.com>
Tue, 7 Feb 2017 00:39:09 +0000 (19:39 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 16 Mar 2017 02:18:48 +0000 (02:18 +0000)
commit269561fe408d90a947f74ffe0c7572d7cc2f82b9
tree10c82f84eee9421ea198bff42d3d2221423a160e
parent9ced4235b06ae65916f12f157e83bd985aa9460a
btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls

commit 2a362249187a8d0f6d942d6e1d763d150a296f47 upstream.

Commit 4c63c2454ef incorrectly assumed that returning -ENOIOCTLCMD would
cause the native ioctl to be called.  The ->compat_ioctl callback is
expected to handle all ioctls, not just compat variants.  As a result,
when using 32-bit userspace on 64-bit kernels, everything except those
three ioctls would return -ENOTTY.

Fixes: 4c63c2454ef ("btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl")
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/btrfs/ioctl.c