From: kernel test robot <oliver.sang@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>,
<linux-xfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [xfs] 0ff51a1fd7: WARNING:at_arch/x86/mm/fault.c:#do_user_addr_fault
Date: Thu, 26 Mar 2026 15:41:39 +0800 [thread overview]
Message-ID: <202603261509.7544794b-lkp@intel.com> (raw)
Hello,
Since this change is targeted for the 2025 LTS kernel, and we don't have
sufficient knowledge to evaluate whether the randconfig we used creates overly
corner-case tests or can reveal genuine issues, we are providing this report
for your information only.
The randconfig doesn't set CONFIG_JUMP_LABEL, but this config will be selected
by the following configuration:
--- /pkg/linux/i386-randconfig-011-20260324/clang-20/21d59d00221e4ecbcb597eec0021c667477d3335/.config 2026-03-25 22:14:50.695300028 +0800
+++ /pkg/linux/i386-randconfig-011-20260324/clang-20/0ff51a1fd786f47ba435ede6209046959bad54a8/.config 2026-03-25 22:14:53.775551568 +0800
@@ -666,7 +666,8 @@ CONFIG_GENERIC_IRQ_ENTRY=y
CONFIG_GENERIC_SYSCALL=y
CONFIG_GENERIC_ENTRY=y
CONFIG_KPROBES=y
-# CONFIG_JUMP_LABEL is not set
+CONFIG_JUMP_LABEL=y
+# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_STATIC_CALL_SELFTEST is not set
CONFIG_OPTPROBES=y
CONFIG_UPROBES=y
@@ -5125,7 +5126,13 @@ CONFIG_XFS_SUPPORT_ASCII_CI=y
CONFIG_XFS_QUOTA=y
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
-# CONFIG_XFS_ONLINE_SCRUB is not set
+CONFIG_XFS_DRAIN_INTENTS=y
+CONFIG_XFS_LIVE_HOOKS=y
+CONFIG_XFS_MEMORY_BUFS=y
+CONFIG_XFS_BTREE_IN_MEM=y
+CONFIG_XFS_ONLINE_SCRUB=y
+CONFIG_XFS_ONLINE_SCRUB_STATS=y
+CONFIG_XFS_ONLINE_REPAIR=y
CONFIG_XFS_DEBUG=y
# CONFIG_XFS_DEBUG_EXPENSIVE is not set
# CONFIG_XFS_ASSERT_FATAL is not set
During boot tests, we discovered the following issue that does not appear in the
parent commit.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb-i386/boot/quantal-i386-core-20190426.cgz/i386-randconfig-011-20260324/clang-20/1
21d59d00221e4ecb 0ff51a1fd786f47ba435ede6209
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:50 42% 21:50 dmesg.BUG:kernel_NULL_pointer_dereference,address
:50 58% 29:50 dmesg.BUG:unable_to_handle_page_fault_for_address
:50 100% 50:50 dmesg.EIP:do_int80_syscall_32
:50 100% 50:50 dmesg.EIP:do_user_addr_fault
:50 100% 50:50 dmesg.Kernel_panic-not_syncing:Fatal_exception
:50 100% 50:50 dmesg.Oops
:50 100% 50:50 dmesg.WARNING:at_arch/x86/mm/fault.c:#do_user_addr_fault
:50 100% 50:50 dmesg.boot_failures
below is the full report.
kernel test robot noticed "WARNING:at_arch/x86/mm/fault.c:#do_user_addr_fault" on:
commit: 0ff51a1fd786f47ba435ede6209046959bad54a8 ("xfs: enable online fsck by default in Kconfig")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linux-next/master 09c0f7f1bcdbc3c37a5a760cbec76bf18f278406]
in testcase: boot
config: i386-randconfig-011-20260324
compiler: clang-20
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(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/202603261509.7544794b-lkp@intel.com
[ 6.797604][ T68] ------------[ cut here ]------------
[ 6.799213][ T68] WARNING: CPU: 1 PID: 68 at arch/x86/mm/fault.c:1276 do_user_addr_fault (ld-temp.o:?)
[ 6.799922][ T68] Modules linked in:
[ 6.800237][ T68] CPU: 1 UID: 0 PID: 68 Comm: rc.local Not tainted 6.17.0-rc4-00013-g0ff51a1fd786 #1 PREEMPTLAZY
[ 6.801014][ T68] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 6.801760][ T68] EIP: do_user_addr_fault (ld-temp.o:?)
[ 6.802134][ T68] Code: 15 fe ff ff 89 f9 ff 75 f0 e8 87 05 00 00 83 c4 04 e9 03 fe ff ff 89 f9 89 da ff 75 f0 e8 b3 01 00 00 83 c4 04 e9 ef fd ff ff <0f> 0b 89 f9 89 da ff 75 f0 e8 9d 04 00 00 83 c4 04 e9 d9 fd ff ff
All code
========
0: 15 fe ff ff 89 adc $0x89fffffe,%eax
5: f9 stc
6: ff 75 f0 push -0x10(%rbp)
9: e8 87 05 00 00 call 0x595
e: 83 c4 04 add $0x4,%esp
11: e9 03 fe ff ff jmp 0xfffffffffffffe19
16: 89 f9 mov %edi,%ecx
18: 89 da mov %ebx,%edx
1a: ff 75 f0 push -0x10(%rbp)
1d: e8 b3 01 00 00 call 0x1d5
22: 83 c4 04 add $0x4,%esp
25: e9 ef fd ff ff jmp 0xfffffffffffffe19
2a:* 0f 0b ud2 <-- trapping instruction
2c: 89 f9 mov %edi,%ecx
2e: 89 da mov %ebx,%edx
30: ff 75 f0 push -0x10(%rbp)
33: e8 9d 04 00 00 call 0x4d5
38: 83 c4 04 add $0x4,%esp
3b: e9 d9 fd ff ff jmp 0xfffffffffffffe19
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: 89 f9 mov %edi,%ecx
4: 89 da mov %ebx,%edx
6: ff 75 f0 push -0x10(%rbp)
9: e8 9d 04 00 00 call 0x4ab
e: 83 c4 04 add $0x4,%esp
11: e9 d9 fd ff ff jmp 0xfffffffffffffdef
[ 6.807700][ T68] EAX: 80000000 EBX: 00000000 ECX: 00000000 EDX: 4448bf00
[ 6.808245][ T68] ESI: 434eff2c EDI: 434eff2c EBP: 434eff08 ESP: 434efedc
[ 6.808774][ T68] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010046
[ 6.809317][ T68] CR0: 80050033 CR2: 3fb783bc CR3: 10d4a000 CR4: 000406b0
[ 6.809855][ T68] Call Trace:
[ 6.810103][ T68] ? do_execveat_common (ld-temp.o:?)
[ 6.810486][ T68] ? exc_page_fault (ld-temp.o:?)
[ 6.810930][ T68] ? pvclock_clocksource_read_nowd (ld-temp.o:?)
[ 6.811381][ T68] ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 6.811784][ T68] ? handle_exception (arch/x86/entry/entry_32.S:1048)
[ 6.812169][ T68] ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 6.812538][ T68] ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 6.812897][ T68] ? pvclock_clocksource_read_nowd (ld-temp.o:?)
[ 6.813339][ T68] ? do_int80_syscall_32 (ld-temp.o:?)
[ 6.813756][ T68] ? pvclock_clocksource_read_nowd (ld-temp.o:?)
[ 6.814194][ T68] ? do_int80_syscall_32 (ld-temp.o:?)
[ 6.814581][ T68] ? irqentry_exit (ld-temp.o:?)
[ 6.814941][ T68] ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 6.815276][ T68] ? entry_INT80_32 (arch/x86/entry/entry_32.S:945)
[ 6.815646][ T68] irq event stamp: 3394
[ 6.815980][ T68] hardirqs last enabled at (3393): bprm_execve (ld-temp.o:?)
[ 6.816583][ T68] hardirqs last disabled at (3394): do_int80_syscall_32 (ld-temp.o:?)
[ 6.817250][ T68] softirqs last enabled at (3354): __do_softirq (ld-temp.o:?)
[ 6.817842][ T68] softirqs last disabled at (3339): __do_softirq (ld-temp.o:?)
[ 6.818418][ T68] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260326/202603261509.7544794b-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-26 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603261509.7544794b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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