From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 4/4] fuzzy: don't fail on compressed metadumps
Date: Sat, 17 Dec 2022 12:06:51 -0800 [thread overview]
Message-ID: <Y54hW+ecHDNtC7M9@magnolia> (raw)
In-Reply-To: <20221217103333.knedx24lltmnodxq@zlang-mailbox>
On Sat, Dec 17, 2022 at 06:33:33PM +0800, Zorro Lang wrote:
> On Sat, Dec 17, 2022 at 03:03:29PM +0800, Zorro Lang wrote:
> > On Tue, Dec 13, 2022 at 11:45:33AM -0800, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > >
> > > This line in __scratch_xfs_fuzz_mdrestore:
> > >
> > > test -e "${POPULATE_METADUMP}"
> > >
> > > Breaks spectacularly on a setup that uses DUMP_COMPRESSOR to compress
> > > the metadump files, because the metadump files get the compression
> > > program added to the name (e.g. "${POPULATE_METADUMP}.xz"). The check
> > > is wrong, and since the naming policy is an implementation detail of
> > > _xfs_mdrestore, let's get rid of the -e test.
> > >
> > > However, we still need a way to fail the test if the metadump cannot be
> > > restored. _xfs_mdrestore returns nonzero on failure, so use that
> > > instead.
> > >
> > > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > > ---
> >
> > Looks good to me,
> > Reviewed-by: Zorro Lang <zlang@redhat.com>
> >
> > > common/fuzzy | 5 ++---
> > > 1 file changed, 2 insertions(+), 3 deletions(-)
> > >
> > >
> > > diff --git a/common/fuzzy b/common/fuzzy
> > > index e634815eec..49c850f2d5 100644
> > > --- a/common/fuzzy
> > > +++ b/common/fuzzy
> > > @@ -156,10 +156,9 @@ __scratch_xfs_fuzz_unmount()
> > > # Restore metadata to scratch device prior to field-fuzzing.
> > > __scratch_xfs_fuzz_mdrestore()
> > > {
> > > - test -e "${POPULATE_METADUMP}" || _fail "Need to set POPULATE_METADUMP"
> > > -
> > > __scratch_xfs_fuzz_unmount
> > > - _xfs_mdrestore "${POPULATE_METADUMP}" "${SCRATCH_DEV}" compress
> > > + _xfs_mdrestore "${POPULATE_METADUMP}" "${SCRATCH_DEV}" compress || \
>
> FYI, I've also removed the "compress" parameter according to:
> [PATCH v1.1 3/4] common/populate: move decompression code to _{xfs,ext4}_mdrestore
> When I merged this patch.
Thank you! Sorry for the mess. :/
--D
> > > + _fail "${POPULATE_METADUMP}: Could not find metadump to restore?"
> > > }
> > >
> > > __fuzz_notify() {
> > >
>
prev parent reply other threads:[~2022-12-17 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:45 [PATCHSET 0/4] fstests: fix broken fuzzing xfs_mdrestore calls Darrick J. Wong
2022-12-13 19:45 ` [PATCH 1/4] common/populate: create helpers to handle restoring metadumps Darrick J. Wong
2022-12-17 6:24 ` Zorro Lang
2022-12-13 19:45 ` [PATCH 2/4] common/xfs: create a helper for restoring metadumps to the scratch devs Darrick J. Wong
2022-12-17 6:32 ` Zorro Lang
2022-12-13 19:45 ` [PATCH 3/4] common/populate: move decompression code to _{xfs,ext4}_mdrestore Darrick J. Wong
2022-12-17 6:50 ` Zorro Lang
2022-12-17 8:11 ` Darrick J. Wong
2022-12-17 8:18 ` [PATCH v1.1 " Darrick J. Wong
2022-12-17 9:50 ` Zorro Lang
2022-12-13 19:45 ` [PATCH 4/4] fuzzy: don't fail on compressed metadumps Darrick J. Wong
2022-12-17 7:03 ` Zorro Lang
2022-12-17 10:33 ` Zorro Lang
2022-12-17 20:06 ` Darrick J. Wong [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=Y54hW+ecHDNtC7M9@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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