From: kernel test robot <oliver.sang@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [hare-scsi-devel:configfs-ns.v5] [fs/configfs] 7aae6b1018: Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]SMP_KASAN_PTI
Date: Fri, 29 May 2026 16:59:32 +0800 [thread overview]
Message-ID: <202605291631.40385aeb-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]SMP_KASAN_PTI" on:
commit: 7aae6b1018fb4655e80345c84a0c000ef5c4a7fe ("fs/configfs: separate out configfs_{link,unlink}_root()")
https://git.kernel.org/cgit/linux/kernel/git/hare/scsi-devel.git configfs-ns.v5
in testcase: boot
config: x86_64-randconfig-001-20260529
compiler: gcc-14
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(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/202605291631.40385aeb-lkp@intel.com
[ 17.291164][ T1] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
[ 17.292114][ T1] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
[ 17.292114][ T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.1.0-rc2-00032-g7aae6b1018fb #1 PREEMPT(full)
[ 17.302193][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 17.302193][ T1] RIP: configfs_unlink_root+0x204/0x580
[ 17.302193][ T1] Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 09 03 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 63 68 49 8d 7c 24 04 48 89 fa 48 c1 ea 03 <0f> b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 51
All code
========
0: ff lcall (bad)
1: df 48 c1 fisttps -0x3f(%rax)
4: ea (bad)
5: 03 80 3c 02 00 0f add 0xf00023c(%rax),%eax
b: 85 09 test %ecx,(%rcx)
d: 03 00 add (%rax),%eax
f: 00 48 b8 add %cl,-0x48(%rax)
12: 00 00 add %al,(%rax)
14: 00 00 add %al,(%rax)
16: 00 fc add %bh,%ah
18: ff lcall (bad)
19: df 4c 8b 63 fisttps 0x63(%rbx,%rcx,4)
1d: 68 49 8d 7c 24 push $0x247c8d49
22: 04 48 add $0x48,%al
24: 89 fa mov %edi,%edx
26: 48 c1 ea 03 shr $0x3,%rdx
2a:* 0f b6 14 02 movzbl (%rdx,%rax,1),%edx <-- trapping instruction
2e: 48 89 f8 mov %rdi,%rax
31: 83 e0 07 and $0x7,%eax
34: 83 c0 03 add $0x3,%eax
37: 38 d0 cmp %dl,%al
39: 7c 08 jl 0x43
3b: 84 d2 test %dl,%dl
3d: 0f .byte 0xf
3e: 85 .byte 0x85
3f: 51 push %rcx
Code starting with the faulting instruction
===========================================
0: 0f b6 14 02 movzbl (%rdx,%rax,1),%edx
4: 48 89 f8 mov %rdi,%rax
7: 83 e0 07 and $0x7,%eax
a: 83 c0 03 add $0x3,%eax
d: 38 d0 cmp %dl,%al
f: 7c 08 jl 0x19
11: 84 d2 test %dl,%dl
13: 0f .byte 0xf
14: 85 .byte 0x85
15: 51 push %rcx
[ 17.302193][ T1] RSP: 0000:ffffc9000001fcc0 EFLAGS: 00010247
[ 17.302193][ T1] RAX: dffffc0000000000 RBX: ffff8881005f0eb0 RCX: ffffc9000001fbb4
[ 17.302193][ T1] RDX: 0000000000000000 RSI: ffffffff8516f240 RDI: 0000000000000004
[ 17.302193][ T1] RBP: ffffc9000001fd00 R08: 0000000000000001 R09: ffffed10200bd765
[ 17.302193][ T1] R10: ffff8881005ebb2b R11: 0000000000000000 R12: 0000000000000000
[ 17.302193][ T1] R13: ffff8881005eba70 R14: ffff8881005f0f18 R15: ffff8881005ebad8
[ 17.302193][ T1] FS: 0000000000000000(0000) GS:ffff888799493000(0000) knlGS:0000000000000000
[ 17.302193][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 17.302193][ T1] CR2: 0000000000000000 CR3: 0000000004ce4000 CR4: 00000000000406b0
[ 17.302193][ T1] Call Trace:
[ 17.302193][ T1] <TASK>
[ 17.302193][ T1] configfs_unregister_subsystem (kbuild/src/fs/configfs/dir.c:1957)
[ 17.302193][ T1] ? nvl_gpio_driver_init (gpio-novalake-events.c:?)
[ 17.302193][ T1] gpio_virtuser_init (kbuild/src/drivers/gpio/gpio-virtuser.c:1789)
[ 17.302193][ T1] do_one_initcall (kbuild/src/init/main.c:1392)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260529/202605291631.40385aeb-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-29 8:59 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=202605291631.40385aeb-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=hare@suse.de \
--cc=linux-fsdevel@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