public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org,
	fstests@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCH 1/2] xfs: test what happens when we reset the root dir and it has xattrs
Date: Wed, 28 Apr 2021 17:31:35 -0700	[thread overview]
Message-ID: <20210429003135.GL3122264@magnolia> (raw)
In-Reply-To: <YImdkx6ofgQ1t8CD@bfoster>

On Wed, Apr 28, 2021 at 01:38:27PM -0400, Brian Foster wrote:
> On Tue, Apr 27, 2021 at 09:08:43PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Make sure that we can reset the root directory and the xattrs are erased
> > properly.
> > 
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> >  tests/xfs/757     |   63 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  tests/xfs/757.out |    7 ++++++
> >  tests/xfs/group   |    1 +
> >  3 files changed, 71 insertions(+)
> >  create mode 100755 tests/xfs/757
> >  create mode 100644 tests/xfs/757.out
> > 
> > 
> > diff --git a/tests/xfs/757 b/tests/xfs/757
> > new file mode 100755
> > index 00000000..0b9914f6
> > --- /dev/null
> > +++ b/tests/xfs/757
> > @@ -0,0 +1,63 @@
> > +#! /bin/bash
> > +# SPDX-License-Identifier: GPL-2.0-or-later
> > +# Copyright (c) 2021 Oracle.  All Rights Reserved.
> > +#
> > +# FS QA Test No. 757
> > +#
> > +# Make sure that attrs are handled properly when repair has to reset the root
> > +# directory.
> > +#
> > +seq=`basename $0`
> > +seqres=$RESULT_DIR/$seq
> > +echo "QA output created by $seq"
> > +
> > +here=`pwd`
> > +tmp=/tmp/$$
> > +status=1	# failure is the default!
> > +trap "_cleanup; exit \$status" 0 1 2 3 7 15
> > +
> > +_cleanup()
> > +{
> > +	cd /
> > +	rm -rf $tmp.*
> > +}
> > +
> > +# get standard environment, filters and checks
> > +. ./common/rc
> > +. ./common/filter
> > +. ./common/populate
> > +. ./common/fuzzy
> > +
> > +# real QA test starts here
> > +_supported_fs xfs
> > +_require_scratch_nocheck
> > +
> > +rm -f $seqres.full
> > +
> > +echo "Format and populate btree attr root dir"
> > +_scratch_mkfs > "$seqres.full" 2>&1
> > +_scratch_mount
> > +
> > +blksz="$(stat -f -c '%s' "${SCRATCH_MNT}")"
> > +__populate_create_attr "${SCRATCH_MNT}" "$((64 * blksz / 40))" true
> > +_scratch_unmount
> > +
> > +echo "Break the root directory"
> > +_scratch_xfs_fuzz_metadata_field core.mode zeroes 'sb 0' 'addr rootino' >> $seqres.full 2>&1
> > +
> > +echo "Detect bad root directory"
> > +_scratch_xfs_repair -n >> $seqres.full 2>&1 && \
> > +	echo "Should have detected bad root dir"
> > +
> > +echo "Fix bad root directory"
> > +_scratch_xfs_repair >> $seqres.full 2>&1
> > +
> > +echo "Detect fixed root directory"
> > +_scratch_xfs_repair -n >> $seqres.full 2>&1
> > +
> > +echo "Mount test"
> > +_scratch_mount
> > +
> 
> Is the regression test here that attrs are erased after this sequence
> (as suggested in the commit log), or that the fs mounts, or both? I'm
> basically just wondering if we should also dump the xattrs on the root
> dir as a last step (and expect NULL output)..? That aside:

I've been racking my brain trying to remember where this test came from.
IIRC it was some xfs_repair segfault bug that I came across last
September.  It would manifest if the root dir had xattrs attached and
repair decided to nuke the root directory, but there aren't any obvious
patches, and I've totally forgotten the original context.  It might have
related to Dave or someone noticing that things didn't quite work with a
filesystem that had selinux enabled and the root dir got corrupt...?

Either way, thanks for the reviews :)

--D

> Reviewed-by: Brian Foster <bfoster@redhat.com>
> 
> > +# success, all done
> > +status=0
> > +exit
> > diff --git a/tests/xfs/757.out b/tests/xfs/757.out
> > new file mode 100644
> > index 00000000..9f3aed5a
> > --- /dev/null
> > +++ b/tests/xfs/757.out
> > @@ -0,0 +1,7 @@
> > +QA output created by 757
> > +Format and populate btree attr root dir
> > +Break the root directory
> > +Detect bad root directory
> > +Fix bad root directory
> > +Detect fixed root directory
> > +Mount test
> > diff --git a/tests/xfs/group b/tests/xfs/group
> > index 731f869c..76e31167 100644
> > --- a/tests/xfs/group
> > +++ b/tests/xfs/group
> > @@ -528,5 +528,6 @@
> >  537 auto quick
> >  538 auto stress
> >  539 auto quick mount
> > +757 auto quick attr repair
> >  908 auto quick bigtime
> >  909 auto quick bigtime quota
> > 
> 

  reply	other threads:[~2021-04-29  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  4:08 [PATCHSET 0/2] fstests: test xfsprogs regression fixed in 5.12 Darrick J. Wong
2021-04-28  4:08 ` [PATCH 1/2] xfs: test what happens when we reset the root dir and it has xattrs Darrick J. Wong
2021-04-28 17:38   ` Brian Foster
2021-04-29  0:31     ` Darrick J. Wong [this message]
2021-04-28  4:08 ` [PATCH 2/2] xfs/010: filter out bad finobt levels complaint Darrick J. Wong
2021-04-28 17:38   ` Brian Foster

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=20210429003135.GL3122264@magnolia \
    --to=djwong@kernel.org \
    --cc=bfoster@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --cc=guaneryu@gmail.com \
    --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