Skip to content

Commit

Permalink
Btrfs: fix type mismatch in find_free_extent()
Browse files Browse the repository at this point in the history
data parameter should be u64 because a full-sized chunk flags field is
passed instead of 0/1 for distinguishing data from metadata.  All
underlying functions expect u64.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
  • Loading branch information
Ilya Dryomov authored and Chris Mason committed Jun 25, 2011
1 parent 1973f0f commit e0f5406
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions fs/btrfs/extent-tree.c
Original file line number Diff line number Diff line change
Expand Up @@ -4842,7 +4842,7 @@ static noinline int find_free_extent(struct btrfs_trans_handle *trans,
u64 num_bytes, u64 empty_size,
u64 search_start, u64 search_end,
u64 hint_byte, struct btrfs_key *ins,
int data)
u64 data)
{
int ret = 0;
struct btrfs_root *root = orig_root->fs_info->extent_root;
Expand All @@ -4869,7 +4869,7 @@ static noinline int find_free_extent(struct btrfs_trans_handle *trans,

space_info = __find_space_info(root->fs_info, data);
if (!space_info) {
printk(KERN_ERR "No space info for %d\n", data);
printk(KERN_ERR "No space info for %llu\n", data);
return -ENOSPC;
}

Expand Down

0 comments on commit e0f5406

Please sign in to comment.