From: Bill O'Donnell <billodo@redhat.com>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/191: fix xattr leaf block emptying on 64k blocksized fses
Date: Thu, 2 Feb 2023 18:33:20 -0600 [thread overview]
Message-ID: <Y9xWUG7G5eDsLlL/@redhat.com> (raw)
In-Reply-To: <20230202210940.95791-1-ailiop@suse.com>
On Thu, Feb 02, 2023 at 10:09:40PM +0100, Anthony Iliopoulos wrote:
> This test is failing on filesystems with 64k blocksize since the leaf
> hdr.firstused field is 16 bit and as such trying to reset it to $dbsize
> overflows and is rejected by xfs_db. The leaf is never properly resetted
> and the discrepancy is picked up by xfs_repair, thus failing the test.
>
> Fix it by setting it to XFS_ATTR3_LEAF_NULLOFF (0) as this is the proper
> on-disk value to indicate an empty leaf on 64k blocksized fses.
>
> Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
On my ppc64le box, this patch fixes the problem nicely. Thanks!
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>
> ---
> tests/xfs/191 | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/tests/xfs/191 b/tests/xfs/191
> index 4f0a9b9eeef5..8dd875fcd28b 100755
> --- a/tests/xfs/191
> +++ b/tests/xfs/191
> @@ -78,10 +78,20 @@ make_empty_leaf() {
>
> base=$(_scratch_xfs_get_metadata_field "hdr.freemap[0].base" "inode $inum" "ablock 0")
>
> + # 64k dbsize is a special case since it overflows the 16 bit firstused
> + # field and it needs to be set to the special XFS_ATTR3_LEAF_NULLOFF (0)
> + # value to indicate a null leaf. For more details see kernel commit:
> + # e87021a2bc10 ("xfs: use larger in-core attr firstused field and detect overflow").
> + if [ $dbsize -eq 65536 ]; then
> + firstused=0;
> + else
> + firstused=$dbsize;
> + fi
> +
> _scratch_xfs_db -x -c "inode $inum" -c "ablock 0" \
> -c "write -d hdr.count 0" \
> -c "write -d hdr.usedbytes 0" \
> - -c "write -d hdr.firstused $dbsize" \
> + -c "write -d hdr.firstused $firstused" \
> -c "write -d hdr.freemap[0].size $((dbsize - base))" \
> -c print >> $seqres.full
> }
> --
> 2.35.3
>
prev parent reply other threads:[~2023-02-03 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 21:09 [PATCH] xfs/191: fix xattr leaf block emptying on 64k blocksized fses Anthony Iliopoulos
2023-02-03 0:04 ` Darrick J. Wong
2023-02-03 0:33 ` Bill O'Donnell [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=Y9xWUG7G5eDsLlL/@redhat.com \
--to=billodo@redhat.com \
--cc=ailiop@suse.com \
--cc=fstests@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