summaryrefslogtreecommitdiff
path: root/fs/xfs/xfs_bmap_item.c
diff options
context:
space:
mode:
authorDarrick J. Wong <djwong@kernel.org>2022-10-24 10:11:02 -0700
committerDarrick J. Wong <djwong@kernel.org>2022-10-31 08:51:45 -0700
commit47ba8cc7b4f82c927cec3ad7c7392e4c45c81c56 (patch)
tree3bfb0e1dae91f9b1ad548c152f8cc38b2551d83a /fs/xfs/xfs_bmap_item.c
parente07ee6fe21f47cfd72ae566395c67a80e7c66163 (diff)
xfs: fix incorrect return type for fsdax fault handlersxfs-6.1-fixes_2022-10-31xfs-6.1-fixes-2
The kernel robot complained about this: >> fs/xfs/xfs_file.c:1266:31: sparse: sparse: incorrect type in return expression (different base types) @@ expected int @@ got restricted vm_fault_t @@ fs/xfs/xfs_file.c:1266:31: sparse: expected int fs/xfs/xfs_file.c:1266:31: sparse: got restricted vm_fault_t fs/xfs/xfs_file.c:1314:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted vm_fault_t [usertype] ret @@ got int @@ fs/xfs/xfs_file.c:1314:21: sparse: expected restricted vm_fault_t [usertype] ret fs/xfs/xfs_file.c:1314:21: sparse: got int Fix the incorrect return type for these two functions. While we're at it, make the !fsdax version return VM_FAULT_SIGBUS because a zero return value will cause some callers to try to lock vmf->page, which we never set here. Fixes: ea6c49b784f0 ("xfs: support CoW in fsdax mode") Signed-off-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Dave Chinner <dchinner@redhat.com>
Diffstat (limited to 'fs/xfs/xfs_bmap_item.c')
0 files changed, 0 insertions, 0 deletions