diff options
| author | David Sterba <[email protected]> | 2023-05-24 23:04:34 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2023-06-19 11:59:30 +0000 |
| commit | 7dde7a8ab32417f28c4ac0111f8a8389fc0501ff (patch) | |
| tree | 393611dac520ac6d40f0a4be225abc8b436faf62 /fs/btrfs/dev-replace.c | |
| parent | btrfs: open code set_extent_bits (diff) | |
| download | kernel-7dde7a8ab32417f28c4ac0111f8a8389fc0501ff.tar.gz kernel-7dde7a8ab32417f28c4ac0111f8a8389fc0501ff.zip | |
btrfs: drop NOFAIL from set_extent_bit allocation masks
The __GFP_NOFAIL passed to set_extent_bit first appeared in 2010
(commit f0486c68e4bd9a ("Btrfs: Introduce contexts for metadata
reservation")), without any explanation why it would be needed.
Meanwhile we've updated the semantics of set_extent_bit to handle failed
allocations and do unlock, sleep and retry if needed. The use of the
NOFAIL flag is also an outlier, we never want any of the set/clear
extent bit helpers to fail, they're used for many critical changes like
extent locking, besides the extent state bit changes.
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'fs/btrfs/dev-replace.c')
0 files changed, 0 insertions, 0 deletions