From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com, sandeen@redhat.com
Subject: [PATCH v3 0/2] remove _wipe_fs and add a new dump test
Date: Tue, 19 Apr 2022 01:03:24 +0800 [thread overview]
Message-ID: <20220418170326.425762-1-zlang@redhat.com> (raw)
As we talked in version~2 of [PATCH 2/2] [1], Dave said "common/dump::_wipe_fs()
is effectively just _scratch_mkfs() followed by mounting it. It does not need
to exist at all." So we decided to remove _wipe_fs() function entirely from
all xfstests cases.
So:
[PATCH v3 1/2] is a new patch to remove _wipe_fs.
[PATCH v3 2/2] avoid using WIPE_FS parameter
[1]
https://lore.kernel.org/fstests/20220411083433.omc3yvn75k5ap6zk@zlang-mailbox/
Thanks,
Zorro
next reply other threads:[~2022-04-18 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 17:03 Zorro Lang [this message]
2022-04-18 17:03 ` [PATCH v3 1/2] fstests: remove _wipe_fs from dump testing entirely Zorro Lang
2022-04-19 15:56 ` Darrick J. Wong
2022-04-19 18:16 ` Zorro Lang
2022-04-18 17:03 ` [PATCH v3 2/2] xfs: test xfsdump when an inode < root inode is present Zorro Lang
2022-04-19 15:57 ` Darrick J. Wong
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=20220418170326.425762-1-zlang@redhat.com \
--to=zlang@redhat.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@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