From: Yuto Ohnuki <ytohnuki@amazon.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Carlos Maiolino <cem@kernel.org>, <linux-xfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: check directory data block header padding in scrub
Date: Wed, 8 Apr 2026 18:03:25 +0100 [thread overview]
Message-ID: <adaKXX0JAm5e9E6p@c889f3b07a0a.ant.amazon.com> (raw)
In-Reply-To: <20260406152110.GA1048989@frogsfrogsfrogs>
On Mon, Apr 06, 2026 at 08:21:10AM -0700, Darrick J. Wong wrote:
Hi Darrick,
Thank you for the review.
> But where do we set xfs_dir3_data_hdr.pad to zero? xfs_dir3_data_init
> does not seem to do this...
Thank you for pointing that out. I'll fix xfs_dir3_data_init to zero
the full xfs_dir3_data_hdr instead of just xfs_dir3_blk_hdr so that
the pad field is covered by the memset.
> ...and even if there is code that does the zero-initialization, it's
> possible that old kernels wrote out garbage in the pad field and were
> quite ok with that. At best you can set XFS_SCRUB_OFLAG_PREEN to
> indicate that this kernel should clean it out.
>
> (For that you'd also want to add a new xchk_fblock_set_corrupt helper to
> record which block tripped the "optimization possible" message.)
>
> --D
>
Understood. I'll switch to xchk_fblock_set_preen and add the missing
helper for that.
I'll send a v2 with these changes.
Thanks,
Yuto
Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg, R.C.S. Luxembourg B186284
Amazon Web Services EMEA SARL, Irish Branch, One Burlington Plaza, Burlington Road, Dublin 4, Ireland, branch registration number 908705
prev parent reply other threads:[~2026-04-08 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 12:50 [PATCH] xfs: check directory data block header padding in scrub Yuto Ohnuki
2026-04-06 15:21 ` Darrick J. Wong
2026-04-08 17:03 ` Yuto Ohnuki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adaKXX0JAm5e9E6p@c889f3b07a0a.ant.amazon.com \
--to=ytohnuki@amazon.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox