From: Dave Chinner <dgc@kernel.org>
To: Yuto Ohnuki <ytohnuki@amazon.com>
Cc: Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xfs: check da node block pad field during scrub
Date: Thu, 9 Apr 2026 07:40:17 +1000 [thread overview]
Message-ID: <adbLQXN3g5XChaJL@dread> (raw)
In-Reply-To: <20260408174033.4165-2-ytohnuki@amazon.com>
On Wed, Apr 08, 2026 at 06:40:34PM +0100, Yuto Ohnuki wrote:
> The da node block header (xfs_da3_node_hdr) contains a __pad32 field
> that should always be zero. Add a check for this during directory and
> attribute btree scrubbing.
>
> Since old kernels may have written non-zero padding without issues, flag
> this as an optimization opportunity (preen) rather than corruption.
>
> Signed-off-by: Yuto Ohnuki <ytohnuki@amazon.com>
> ---
> Changes in v2:
> - Use xchk_da_set_preen instead of xchk_da_set_corrupt since
> old kernels may have written non-zero padding without issues.
> - Link to v1: https://lore.kernel.org/all/20260404143043.65268-2-ytohnuki@amazon.com/
> ---
> fs/xfs/scrub/dabtree.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/scrub/dabtree.c b/fs/xfs/scrub/dabtree.c
> index 1a71d36898b1..b55922d3e988 100644
> --- a/fs/xfs/scrub/dabtree.c
> +++ b/fs/xfs/scrub/dabtree.c
> @@ -454,7 +454,12 @@ xchk_da_btree_block(
> }
> }
>
> - /* XXX: Check hdr3.pad32 once we know how to fix it. */
> + if (xfs_has_crc(ip->i_mount)) {
> + struct xfs_da3_node_hdr *nodehdr3 = blk->bp->b_addr;
> +
> + if (be32_to_cpu(nodehdr3->__pad32) != 0)
> + xchk_da_set_preen(ds, level);
> + }
Endian conversion not necessary on comaprison to zero.
-Dave.
--
Dave Chinner
dgc@kernel.org
prev parent reply other threads:[~2026-04-08 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 17:40 [PATCH v2] xfs: check da node block pad field during scrub Yuto Ohnuki
2026-04-08 21:40 ` Dave Chinner [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=adbLQXN3g5XChaJL@dread \
--to=dgc@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ytohnuki@amazon.com \
/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