diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2026-10-12 23:06:14 -0700 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-10-14 09:49:28 +0200 |
| commit | 80f13dc7225eec318da7499c7a562d7a34d25e6a (patch) | |
| tree | 0ca72d0b791e7a803f3c7334e218397c8167d572 /tools/perf/scripts/python/stackcollapse.py | |
| parent | ca12256b7f9820aafb361ac496f048d2d4a71c23 (diff) | |
| download | linux-80f13dc7225eec318da7499c7a562d7a34d25e6a.tar.gz linux-80f13dc7225eec318da7499c7a562d7a34d25e6a.zip | |
xfs: reduce new btree slack factor if free space is negative
LOLLM points out that if the incore fdblocks counter is negative, the
assignment to uint64_t will mask this possibly low space situation and
we don't pack the btree blocks as tightly as we probably ought to. If
it's the case that there's some free space and fdblocks is too low due
to an error in the superblock field, then we can end up failing btree
rebuilds due to ENOSPC unnecessarily. This is a corner case, but let's
fix it anyway.
Cc: stable@vger.kernel.org # v6.8
Fixes: be408417630427 ("xfs: implement block reservation accounting for btrees we're staging")
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Assisted-by: LOLLM # finding obvious bugs
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions