diff options
author | Ritesh Harjani <riteshh@linux.ibm.com> | 2020-05-20 12:10:36 +0530 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2020-06-03 23:16:53 -0400 |
commit | 993778306e7901a7286322f25c7c681dd47bede6 (patch) | |
tree | 174a21ba354ba4162ee4c5da7dd6eefafdee6846 /security/keys | |
parent | 8ef123fe02ca0923b01b57bdf639800a23a2faa8 (diff) | |
download | linux-993778306e7901a7286322f25c7c681dd47bede6.tar.bz2 |
ext4: mballoc: use lock for checking free blocks while retrying
Currently while doing block allocation grp->bb_free may be getting
modified if discard is happening in parallel.
For e.g. consider a case where there are lot of threads who have
preallocated lot of blocks and there is a thread which is trying
to discard all of this group's PA. Now it could happen that
we see all of those group's bb_free is zero and fail the allocation
while there is sufficient space if we free up all the PA.
So this patch adds another flag "EXT4_MB_STRICT_CHECK" which will be set
if we are unable to allocate any blocks in the first try (since we may
not have considered blocks about to be discarded from PA lists).
So during retry attempt to allocate blocks we will use ext4_lock_group()
for checking if the group is good or not.
Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
Link: https://lore.kernel.org/r/9cb740a117c958c36596f167b12af1beae9a68b7.1589955723.git.riteshh@linux.ibm.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions