From: "Darrick J. Wong" <djwong@kernel.org>
To: Yuto Ohnuki <ytohnuki@amazon.com>
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: check da node block pad field during scrub
Date: Mon, 6 Apr 2026 08:23:04 -0700 [thread overview]
Message-ID: <20260406152304.GB1048989@frogsfrogsfrogs> (raw)
In-Reply-To: <20260404143043.65268-2-ytohnuki@amazon.com>
On Sat, Apr 04, 2026 at 03:30:44PM +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 so that non-zero padding is flagged as
> corruption.
>
> Signed-off-by: Yuto Ohnuki <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..73d5a3bd936a 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. */
Same question as the previous patch -- does xfs_da3_node_create actually
zero out the pad field?
> + 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_corrupt(ds, level);
and same comment about how you can only set xchk_da_set_preen if old
kernels were ok with nonzero __pad32.
--D
> + }
> break;
> default:
> xchk_da_set_corrupt(ds, level);
> --
> 2.50.1
>
>
>
>
> 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
>
>
>
>
next prev parent reply other threads:[~2026-04-06 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 14:30 Yuto Ohnuki
2026-04-06 15:23 ` Darrick J. Wong [this message]
2026-04-08 17:14 ` Yuto Ohnuki
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=20260406152304.GB1048989@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@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
all inboxes | Powered by JetHome®