From: kernel test robot <oliver.sang@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Tejun Heo <tj@kernel.org>, <netdev@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [rhashtable] e1d3422c95: xfstests.generic.417.fail
Date: Thu, 16 Jan 2025 13:15:21 +0800 [thread overview]
Message-ID: <202501161047.39c960cb-lkp@intel.com> (raw)
hi, Breno Leitao,
FYI. we noticed this commit is in linux-next/master. now we noticed some
xfstests tests failed randomly while pass on parent.
xfstests.generic.417 seems have higher rate to fail.
we also noticed a "Corruption of in-memory data" while running this case.
f916e44487f56df4 e1d3422c95f003eba241c176adf
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 kmsg.XFS(sda4):Corruption_of_in-memory_data(#)detected_at_xfs_fs_reserve_ag_blocks[xfs](fs/xfs/xfs_fsops.c:#).Shutting_down_filesystem
:6 67% 4:6 xfstests.generic.044.fail
:6 50% 3:6 xfstests.generic.046.fail
:6 33% 2:6 xfstests.generic.049.fail
:6 100% 6:6 xfstests.generic.417.fail
:6 17% 1:6 xfstests.generic.530.fail
if you want us to test some patch to fix/debug, please let us know. thanks!
Hello,
kernel test robot noticed "xfstests.generic.417.fail" on:
commit: e1d3422c95f003eba241c176adfe593c33e8a8f6 ("rhashtable: Fix potential deadlock by moving schedule_work outside lock")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master e7bb221a638962d487231ac45a6699fb9bb8f9fa]
in testcase: xfstests
version: xfstests-x86_64-8467552f-1_20241215
with following parameters:
disk: 4HDD
fs: xfs
test: generic-scratch-shutdown-metadata-journaling
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202501161047.39c960cb-lkp@intel.com
2025-01-06 13:32:03 export TEST_DIR=/fs/sda1
2025-01-06 13:32:03 export TEST_DEV=/dev/sda1
2025-01-06 13:32:03 export FSTYP=xfs
2025-01-06 13:32:03 export SCRATCH_MNT=/fs/scratch
2025-01-06 13:32:03 mkdir /fs/scratch -p
2025-01-06 13:32:03 export SCRATCH_DEV=/dev/sda4
2025-01-06 13:32:03 export SCRATCH_LOGDEV=/dev/sda2
2025-01-06 13:32:03 sed "s:^:generic/:" //lkp/benchmarks/xfstests/tests/generic-scratch-shutdown-metadata-journaling
2025-01-06 13:32:03 ./check generic/042 generic/043 generic/044 generic/045 generic/046 generic/047 generic/048 generic/049 generic/051 generic/052 generic/054 generic/055 generic/388 generic/392 generic/417 generic/468 generic/505 generic/506 generic/507 generic/508 generic/530
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 lkp-skl-d03 6.13.0-rc2-00035-ge1d3422c95f0 #1 SMP PREEMPT_DYNAMIC Fri Jan 3 20:52:01 CST 2025
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
generic/042 19s
generic/043 25s
generic/044 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/044.out.bad)
--- tests/generic/044.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/044.out.bad 2025-01-06 13:33:27.348535522 +0000
@@ -1 +1,5 @@
QA output created by 044
+mount: /fs/scratch: mount(2) system call failed: Argument list too long.
+ dmesg(1) may have more information after failed mount system call.
+mount /dev/sda4 /fs/scratch failed
+(see /lkp/benchmarks/xfstests/results//generic/044.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/044.out /lkp/benchmarks/xfstests/results//generic/044.out.bad' to see the entire diff)
generic/045 68s
generic/046 55s
generic/047 72s
generic/048 100s
generic/049 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/049.out.bad)
--- tests/generic/049.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/049.out.bad 2025-01-06 13:38:37.515464142 +0000
@@ -1 +1,5 @@
QA output created by 049
+mount: /fs/scratch: mount(2) system call failed: Argument list too long.
+ dmesg(1) may have more information after failed mount system call.
+mount /dev/sda4 /fs/scratch failed
+(see /lkp/benchmarks/xfstests/results//generic/049.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/049.out /lkp/benchmarks/xfstests/results//generic/049.out.bad' to see the entire diff)
generic/051 80s
generic/052 4s
generic/054 67s
generic/055 47s
generic/388 85s
generic/392 10s
generic/417 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/417.out.bad)
--- tests/generic/417.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/417.out.bad 2025-01-06 13:43:36.466161468 +0000
@@ -2,12 +2,7 @@
mount dirty orphans rw, then unmount
open and unlink 200 files with EAs
godown
-check fs consistency
-mount dirty orphans ro, then unmount
-open and unlink 200 files with EAs
-godown
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/417.out /lkp/benchmarks/xfstests/results//generic/417.out.bad' to see the entire diff)
generic/468 8s
generic/505 5s
generic/506 5s
generic/507 10s
generic/508 6s
generic/530 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/530.out.bad)
--- tests/generic/530.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/530.out.bad 2025-01-06 13:44:32.483499358 +0000
@@ -1,2 +1,6 @@
QA output created by 530
silence is golden
+mount: /fs/scratch: mount(2) system call failed: Argument list too long.
+ dmesg(1) may have more information after failed mount system call.
+mount /dev/sda4 /fs/scratch failed
+(see /lkp/benchmarks/xfstests/results//generic/530.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/530.out /lkp/benchmarks/xfstests/results//generic/530.out.bad' to see the entire diff)
Ran: generic/042 generic/043 generic/044 generic/045 generic/046 generic/047 generic/048 generic/049 generic/051 generic/052 generic/054 generic/055 generic/388 generic/392 generic/417 generic/468 generic/505 generic/506 generic/507 generic/508 generic/530
Failures: generic/044 generic/049 generic/417 generic/530
Failed 4 of 21 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250116/202501161047.39c960cb-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-16 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 5:15 kernel test robot [this message]
2025-01-16 9:35 ` [linux-next:master] [rhashtable] e1d3422c95: xfstests.generic.417.fail Breno Leitao
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=202501161047.39c960cb-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).