From: "Theodore Tso" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk.kim@gmail.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net, fstests@vger.kernel.org
Subject: Re: generic/204 is crashing on linux-next when testing f2fs
Date: Tue, 2 Dec 2025 21:17:09 -0500 [thread overview]
Message-ID: <20251203021709.GA71988@macsyma.lan> (raw)
In-Reply-To: <CAOtxgyeik6kgF6SktvFj=anntmJZ_aWneqq1XzLpqpHK1XMb+Q@mail.gmail.com>
On Tue, Dec 02, 2025 at 09:30:44AM -0800, Jaegeuk Kim wrote:
> > For now, I'll exclude generic/204 from the f2fs configs in my test
> > appliance; if you have a chance to take a look at this and let me know
> > when it might be safe to re-neable generic/204 for f2fs, that would be
> > great. Thanks!
>
> Thank you for sharing the report. I didn't hit this in my setup tho, let
> us try to reproduce it first.
I'm not able to reproduce it by running generic/204 by itself; only
when running the full auto group. (See below). The generic/204 test
reformats the scratch partition at the beginning of the test, and
doesn't depend on the test partition. Presumably, a previous test
when running the auto group is somehow setting up generic/204 to fail.
I'll try doing a run with KASAN enabled, in case that gives us some
insight.
- Ted
TESTRUNID: ltm-20251202161646
KERNEL: kernel 6.18.0-rc4-xfstests-kasan-00072-g6fb67ac89690 #314 SMP PREEMPT_DYNAMIC Tue Dec 2 16:05:26 EST 2025 x86_64
CMDLINE: --kernel gs://gce-xfstests/kernel.deb -c f2fs/all -a -C 30 generic/204
CPUS: 2
MEM: 7680
f2fs/default: 30 tests, 6043 seconds
f2fs/encrypt: 30 tests, 6209 seconds
f2fs/compress: 30 tests, 6140 seconds
Totals: 90 tests, 0 skipped, 0 failures, 0 errors, 18392s
FSTESTIMG: gce-xfstests/xfstests-amd64-202512020012
FSTESTPRJ: gce-xfstests
FSTESTVER: blktests 4badb27 (Fri, 31 Oct 2025 19:53:27 +0900)
FSTESTVER: fio fio-3.41 (Fri, 5 Sep 2025 14:21:17 -0600)
FSTESTVER: fsverity v1.7 (Tue, 4 Nov 2025 17:28:17 -0800)
FSTESTVER: ima-evm-utils v1.5 (Mon, 6 Mar 2023 07:40:07 -0500)
FSTESTVER: libaio libaio-0.3.108-82-gb8eadc9 (Thu, 2 Jun 2022 13:33:11 +0200)
FSTESTVER: ltp 20250930 (Tue, 30 Sep 2025 13:53:45 +0200)
FSTESTVER: quota v4.05-77-g22ff3d9 (Tue, 2 Sep 2025 08:12:02 -0400)
FSTESTVER: util-linux v2.41.2 (Mon, 22 Sep 2025 12:56:34 +0200)
FSTESTVER: xfsprogs v6.17.0 (Mon, 20 Oct 2025 16:49:00 +0200)
FSTESTVER: xfstests-bld gce-xfstests-202504292206-34-g84a091b7 (Tue, 2 Dec 2025 00:09:25 -0500)
FSTESTVER: xfstests v2025.11.04-12-g64e3dbda7 (Thu, 13 Nov 2025 19:58:03 -0500)
FSTESTVER: zz_build-distro trixie
FSTESTSET: generic/204
FSTESTOPT: count 30 fail_loop_count 0
next prev parent reply other threads:[~2025-12-03 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 4:39 generic/204 is crashing on linux-next when testing f2fs Theodore Tso
2025-12-02 17:30 ` Jaegeuk Kim
2025-12-03 2:17 ` Theodore Tso [this message]
2025-12-04 17:20 ` Jaegeuk Kim
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=20251203021709.GA71988@macsyma.lan \
--to=tytso@mit.edu \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk.kim@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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