diff options
| author | Andreas Gruenbacher <agruenba@redhat.com> | 2020-10-06 14:29:04 +0200 |
|---|---|---|
| committer | Andreas Gruenbacher <agruenba@redhat.com> | 2021-01-18 16:56:37 +0100 |
| commit | 2fdc2fa21bc72ec06c0c9f0e30b88fe1f2486b75 (patch) | |
| tree | 40f81956526a1394a1628014ed58a26ae3e50ccf /fs/locks.c | |
| parent | 4272006d956f49e428f87c476959318301f2d4d2 (diff) | |
Revert "gfs2: Don't reject a supposedly full bitmap if we have blocks reserved"
This reverts commit e79e0e1428188b24c3b57309ffa54a33c4ae40c4.
It turns out that we're only setting the GBF_FULL flag of a bitmap if we've
been scanning from the beginning of the bitmap until the end and we haven't
found a single free block, and we're not skipping reservations in that process,
either. This means that in gfs2_rbm_find, we can always skip bitmaps with the
GBF_FULL flag set.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions