diff options
| author |   Michal Hocko <mhocko@suse.com> | 2017-01-09 15:39:03 +0100 |
|---|---|---|
| committer |   David Sterba <dsterba@suse.com> | 2017-02-14 15:50:49 +0100 |
| commit | 1aceabf362dc8c54ec7790de7f95d75c1ecb9678 (patch) | |
| tree | c10020a1917d3f405c37d6cdd6a9098a7881bc9c /fs/btrfs/file-item.c | |
| parent | btrfs: fix up misleading GFP_NOFS usage in btrfs_releasepage (diff) | |
| download | wireguard-linux-1aceabf362dc8c54ec7790de7f95d75c1ecb9678.tar.xz wireguard-linux-1aceabf362dc8c54ec7790de7f95d75c1ecb9678.zip | |
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>
Diffstat (limited to 'fs/btrfs/file-item.c')
0 files changed, 0 insertions, 0 deletions