From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/370: don't exclude XFS
Date: Tue, 18 Feb 2025 09:39:12 -0800 [thread overview]
Message-ID: <20250218173912.GK21799@frogsfrogsfrogs> (raw)
In-Reply-To: <20250217063135.3728305-1-hch@lst.de>
On Mon, Feb 17, 2025 at 07:31:35AM +0100, Christoph Hellwig wrote:
> Skipping tests just because a file system is broken is always a bad idea
> as it hides bugs.
>
> (Fortunately despite hiding the bug this is now getting fixed in XFS as
> well).
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> tests/generic/370 | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/tests/generic/370 b/tests/generic/370
> index 8adffd2e9650..8101ef42724e 100755
> --- a/tests/generic/370
> +++ b/tests/generic/370
> @@ -22,14 +22,6 @@ _cleanup()
> [ "$FSTYP" = "btrfs" ] && _fixed_by_kernel_commit 03018e5d8508 \
> "btrfs: fix swap file activation failure due to extents that used to be shared"
>
> -# Skip XFS for now because this exposes an issue that is hard to fix.
> -# See the following threads for details about it:
> -#
> -# https://lore.kernel.org/linux-xfs/CAL3q7H7cURmnkJfUUx44HM3q=xKmqHb80eRdisErD_x8rU4+0Q@mail.gmail.com/
> -# https://lore.kernel.org/fstests/dca49a16a7aacdab831b8895bdecbbb52c0e609c.1733928765.git.fdmanana@suse.com/
> -#
> -_exclude_fs xfs
Needs a _fixed_by_xfs_commit XXXXXXXX "xfs: flush inodegc before swapon"
--D
> -
> _require_scratch_swapfile
> _require_scratch_reflink
> _require_cp_reflink
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-02-18 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 6:31 [PATCH] generic/370: don't exclude XFS Christoph Hellwig
2025-02-18 4:21 ` Zorro Lang
2025-02-18 17:39 ` Darrick J. Wong [this message]
2025-02-19 6:41 ` 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=20250218173912.GK21799@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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