From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>, Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/3] common: remove the $FSYP check in _cleanup_dump
Date: Tue, 28 Jan 2025 11:14:42 -0800 [thread overview]
Message-ID: <20250128191442.GP3557695@frogsfrogsfrogs> (raw)
In-Reply-To: <20250128071315.676272-3-hch@lst.de>
On Tue, Jan 28, 2025 at 08:12:59AM +0100, Christoph Hellwig wrote:
> Despite the comment, _cleanup_dump is only called from xfs specific
> tests, so this is superfluous.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
This patch looks ok, but I have a few extra[neous] comments...
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> common/dump | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/common/dump b/common/dump
> index 50b2ba03c670..3761c16100d8 100644
> --- a/common/dump
> +++ b/common/dump
> @@ -223,12 +223,6 @@ _require_tape()
> #
> _cleanup_dump()
> {
> - # Some tests include this before checking _supported_fs xfs
> - # and the sleeps & checks here get annoying
> - if [ "$FSTYP" != "xfs" ]; then
> - return
> - fi
> -
I went looking in common/dump and I noticed the lack of an explicit
setup routine. Instead, variables and _require calls are done when
sourcing the file. Curiously there's no check for FSTYP==xfs, which I
guess is reasonable for sourced stuff, but I think that should all get
pulled up into _init_dump() or something.
The other thing I noticed is that sourcing common/dump deletes
$seqres.full, which seems like a real bug.
--D
> cd $here
>
> if [ -n "$DEBUGDUMP" ]; then
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-01-28 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:12 remove _supported_fs v2 Christoph Hellwig
2025-01-28 7:12 ` [PATCH 1/3] generic/363: remove _supported_fs xfs Christoph Hellwig
2025-01-28 19:17 ` Darrick J. Wong
2025-01-29 5:26 ` Christoph Hellwig
2025-01-28 7:12 ` [PATCH 2/3] common: remove the $FSYP check in _cleanup_dump Christoph Hellwig
2025-01-28 19:14 ` Darrick J. Wong [this message]
2025-01-29 5:27 ` Christoph Hellwig
2025-01-28 7:13 ` [PATCH 3/3] replace _supported_fs with _exclude_fs Christoph Hellwig
2025-01-28 19:19 ` Darrick J. Wong
2025-01-29 5:28 ` Christoph Hellwig
2025-02-02 13:31 ` Zorro Lang
2025-02-03 6:40 ` Christoph Hellwig
2025-02-04 17:36 ` Zorro Lang
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=20250128191442.GP3557695@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=zlang@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