From: kernel test robot <oliver.sang@intel.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lance Yang <lance.yang@linux.dev>,
Beleswar Padhi <b-padhi@ti.com>, Will Deacon <will@kernel.org>,
Mark Brown <broonie@kernel.org>,
Aishwarya TCV <aishwarya.tcv@arm.com>,
"David Hildenbrand" <david@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linux-mm@kvack.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [mm/huge_memory] adfb6609c6: xfstests.xfs.050.fail
Date: Thu, 13 Nov 2025 16:23:23 +0800 [thread overview]
Message-ID: <202511131537.1a31ee77-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3982 bytes --]
Hello,
kernel test robot noticed "xfstests.xfs.050.fail" on:
commit: adfb6609c6809e107ded9a1cd46f519c882e64ea ("mm/huge_memory: initialise the tags of the huge zero folio")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 24172e0d79900908cf5ebf366600616d29c9b417]
[test failed on linux-next/master 2666975a8905776d306bee01c5d98a0395bda1c9]
in testcase: xfstests
version: xfstests-x86_64-c4980080-1_20251110
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-050
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G 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/202511131537.1a31ee77-lkp@intel.com
2025-11-12 08:41:57 cd /lkp/benchmarks/xfstests
2025-11-12 08:41:58 export TEST_DIR=/fs/sda1
2025-11-12 08:41:58 export TEST_DEV=/dev/sda1
2025-11-12 08:41:58 export FSTYP=xfs
2025-11-12 08:41:58 export SCRATCH_MNT=/fs/scratch
2025-11-12 08:41:58 mkdir /fs/scratch -p
2025-11-12 08:41:58 export SCRATCH_DEV=/dev/sda4
2025-11-12 08:41:58 export SCRATCH_LOGDEV=/dev/sda2
2025-11-12 08:41:58 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2025-11-12 08:41:58 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2025-11-12 08:41:58 echo xfs/050
2025-11-12 08:41:58 ./check xfs/050
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.18.0-rc5-00021-gadfb6609c680 #1 SMP PREEMPT_DYNAMIC Wed Nov 12 16:23:37 CST 2025
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/050 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/050.out.bad)
--- tests/xfs/050.out 2025-11-10 16:50:07.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/050.out.bad 2025-11-12 08:42:21.560701373 +0000
@@ -47,8 +47,6 @@
[NAME] 0 200 1000 00 [--------] 1 4 10 00 [--------] 0 0 0 00 [--------]
*** push past the soft inode limit
-[ROOT] 0 0 0 00 [--------] 3 0 0 00 [--------] 0 0 0 00 [--------]
-[NAME] 0 200 1000 00 [--------] 5 4 10 00 [7 days] 0 0 0 00 [--------]
*** push past the soft block limit
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/050.out /lkp/benchmarks/xfstests/results//xfs/050.out.bad' to see the entire diff)
Ran: xfs/050
Failures: xfs/050
Failed 1 of 1 tests
we observed the test still can pass randomly. as below, it failed 23 times out
of 30 runs for adfb6609c6, we confirmed the left 7 runs really pass.
and parent can always pass.
9a6b60cb147d5396 adfb6609c6809e107ded9a1cd46
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:30 77% 23:30 xfstests.xfs.050.fail
:30 70% 21:30 dmesg.boot_failures
:30 70% 21:30 dmesg.segfault_at_ip_sp_error
another thing is while xfstests.xfs.050 failed, we can normally observe
dmesg.segfault_at_ip_sp_error
the dmesg uploaded to [1] by bot happened not have sefault, one dmesg with
sefault attached FYI.
[ 57.010698][ T5703] xfs_quota[5703]: segfault at 560559699610 ip 00007ff5a817e3c9 sp 00007ffecf38e6d8 error 4 in libc.so.6[1643c9,7ff5a8042000+165000] likely on CPU 2 (core 2, socket 0)
...
[ 69.439214][ T7404] xfs_quota[7404]: segfault at 562ade6ae290 ip 00007f28b30283c9 sp 00007ffe1e8fb188 error 4 in libc.so.6[1643c9,7f28b2eec000+165000] likely on CPU 2 (core 2, socket 0)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251113/202511131537.1a31ee77-lkp@intel.com [1]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: dmesg-segfault.xz --]
[-- Type: application/x-xz, Size: 28796 bytes --]
next reply other threads:[~2025-11-13 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 8:23 kernel test robot [this message]
2025-11-13 9:04 ` [linus:master] [mm/huge_memory] adfb6609c6: xfstests.xfs.050.fail David Hildenbrand (Red Hat)
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=202511131537.1a31ee77-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=aishwarya.tcv@arm.com \
--cc=akpm@linux-foundation.org \
--cc=b-padhi@ti.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=david@redhat.com \
--cc=lance.yang@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.