diff options
| author | Yuto Ohnuki <ytohnuki@amazon.com> | 2026-04-11 17:24:14 +0300 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-04-27 11:36:36 +0300 |
| commit | 8fbb1877dfa5e26bda1baf8cc6abd3f805098486 (patch) | |
| tree | 4e61de70fd9fecffbc5fd28be6acddf59b3b968c /drivers | |
| parent | 00dd8d7ec5253c6273023a0fd6dc08683e0bdfef (diff) | |
| download | linux-8fbb1877dfa5e26bda1baf8cc6abd3f805098486.tar.xz | |
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 'drivers')
0 files changed, 0 insertions, 0 deletions
