btrfs: don't use UAPI types for fiemap callback
authorDavid Sterba <dsterba@suse.com>
Tue, 23 Jun 2020 18:56:12 +0000 (20:56 +0200)
committerDavid Sterba <dsterba@suse.com>
Mon, 27 Jul 2020 10:55:27 +0000 (12:55 +0200)
The fiemap callback is not part of UAPI interface and the prototypes
don't have the __u64 types either.

Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c
fs/btrfs/extent_io.h
fs/btrfs/inode.c

index 1b18960..e3078ed 100644 (file)
@@ -4669,7 +4669,7 @@ static int emit_last_fiemap_cache(struct fiemap_extent_info *fieinfo,
 }
 
 int extent_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
-               __u64 start, __u64 len)
+                 u64 start, u64 len)
 {
        int ret = 0;
        u64 off = start;
index 31c5a6a..00a88f2 100644 (file)
@@ -204,7 +204,7 @@ int btree_write_cache_pages(struct address_space *mapping,
                            struct writeback_control *wbc);
 void extent_readahead(struct readahead_control *rac);
 int extent_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
-               __u64 start, __u64 len);
+                 u64 start, u64 len);
 void set_page_extent_mapped(struct page *page);
 
 struct extent_buffer *alloc_extent_buffer(struct btrfs_fs_info *fs_info,
index 6f8c7d6..e5feefa 100644 (file)
@@ -7946,7 +7946,7 @@ out:
 }
 
 static int btrfs_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
-               __u64 start, __u64 len)
+                       u64 start, u64 len)
 {
        int     ret;