summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorYuto Ohnuki <ytohnuki@amazon.com>2026-04-11 15:24:14 +0100
committerCarlos Maiolino <cem@kernel.org>2026-04-27 10:36:36 +0200
commit8fbb1877dfa5e26bda1baf8cc6abd3f805098486 (patch)
tree4e61de70fd9fecffbc5fd28be6acddf59b3b968c /tools/perf/scripts/python/flamegraph.py
parent00dd8d7ec5253c6273023a0fd6dc08683e0bdfef (diff)
downloadlinux-8fbb1877dfa5e26bda1baf8cc6abd3f805098486.tar.gz
linux-8fbb1877dfa5e26bda1baf8cc6abd3f805098486.zip
xfs: zero directory data block padding on write verification
Old kernels did not zero the pad field in xfs_dir3_data_hdr when initializing directory data blocks, so existing filesystems may have non-zero padding on disk. Zero the pad field in xfs_dir3_data_write_verify alongside the existing LSN and checksum updates. The pad field is pure alignment padding with no runtime meaning, so zeroing it during write verification is safe and has no additional I/O cost. This lets filesystems gradually self-heal stale non-zero padding as directories are modified, without requiring an explicit repair pass. Suggested-by: Dave Chinner <dgc@kernel.org> Signed-off-by: Yuto Ohnuki <ytohnuki@amazon.com> Reviewed-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions