btrfs: drop gfp mask tweaking in try_release_extent_state
authorMichal Hocko <mhocko@suse.com>
Mon, 9 Jan 2017 14:39:03 +0000 (15:39 +0100)
committerDavid Sterba <dsterba@suse.com>
Tue, 14 Feb 2017 14:50:49 +0000 (15:50 +0100)
commit1aceabf362dc8c54ec7790de7f95d75c1ecb9678
treec10020a1917d3f405c37d6cdd6a9098a7881bc9c
parent3ba7ab220e8918176c6f38ee09df86150aca1611
btrfs: drop gfp mask tweaking in try_release_extent_state

try_release_extent_state reduces the gfp mask to GFP_NOFS if it is
compatible. This is true for GFP_KERNEL as well. There is no real
reason to do that though. There is no new lock taken down the
the only consumer of the gfp mask which is
try_release_extent_state
  clear_extent_bit
    __clear_extent_bit
      alloc_extent_state

So this seems just unnecessary and confusing.

Signed-off-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c