diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2026-09-10 22:54:42 -0700 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-09-15 10:11:11 +0200 |
| commit | c54110d814c3e8ed6bbbb5e02874994ed9f668ac (patch) | |
| tree | 6244444daaea6e70a100c74823da45af9003ea5f /tools/perf/tests/shell/test_stackcollapse_python.sh | |
| parent | 46c1b6674a7b3a8385e7fa27f4efc6f45eddf967 (diff) | |
| download | linux-next-c54110d814c3e8ed6bbbb5e02874994ed9f668ac.tar.gz linux-next-c54110d814c3e8ed6bbbb5e02874994ed9f668ac.zip | |
xfs: only flag zero padding for dir3 data blocks, not dir3 block blocks
LOLLM complains that xchk_directory_data_bestfree can be passed a
directory block that is either in "block" or "data" format, but the
check here unconditionally treats the dir3_block and dir3_data blocks as
if they have the same header format (they don't). Consequently, we can
incorrectly set the preen state on dir3_block blocks, which of course
we can't preen away because dir3_block blocks do not have a padding
field. Fix this.
Cc: stable@vger.kernel.org # v7.1-rc4
Fixes: 939919ccddfcc3 ("xfs: check directory data block header padding in scrub")
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/tests/shell/test_stackcollapse_python.sh')
0 files changed, 0 insertions, 0 deletions