From: kernel test robot <oliver.sang@intel.com>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<drbd-dev@lists.linbit.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [drbd] 945807e66a: Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]KASAN_PTI
Date: Sun, 22 Mar 2026 18:07:14 +0800 [thread overview]
Message-ID: <202603221745.8279cd80-lkp@intel.com> (raw)
Hello,
by this commit, we noticed below config diff comparing to parent:
--- /pkg/linux/x86_64-randconfig-006-20260320/clang-20/0c897516a4856d55c75cfdb2b02489b0fc50bdf8/.config 2026-03-20 21:35:52.410943578 +0800
+++ /pkg/linux/x86_64-randconfig-006-20260320/clang-20/945807e66a140e5ee0f919d04e15eadd4cc294be/.config 2026-03-20 16:40:42.155357399 +0800
@@ -1738,6 +1738,12 @@ CONFIG_ZRAM_WRITEBACK=y
# CONFIG_ZRAM_MEMORY_TRACKING is not set
# CONFIG_ZRAM_MULTI_COMP is not set
# CONFIG_BLK_DEV_LOOP is not set
+CONFIG_BLK_DEV_DRBD=y
+# CONFIG_DRBD_FAULT_INJECTION is not set
+CONFIG_BLK_DEV_DRBD_TCP=y
+# CONFIG_BLK_DEV_DRBD_LB_TCP is not set
+# CONFIG_BLK_DEV_DRBD_RDMA is not set
+CONFIG_DRBD_COMPAT_84=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
@@ -5795,6 +5801,7 @@ CONFIG_IOMMU_HELPER=y
CONFIG_FORCE_NR_CPUS=y
CONFIG_GLOB=y
CONFIG_NLATTR=y
+CONFIG_LRU_CACHE=y
CONFIG_CLZ_TAB=y
CONFIG_IRQ_POLL=y
CONFIG_MPILIB=y
as we understand, this commit reenabled drbd. this report is just FYI what we
observed in our tests that there are drbd related issues after this enabling.
kernel test robot noticed "Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]KASAN_PTI" on:
commit: 945807e66a140e5ee0f919d04e15eadd4cc294be ("drbd: remove BROKEN for DRBD")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 785f0eb2f85decbe7c1ef9ae922931f0194ffc2e]
in testcase: boot
config: x86_64-randconfig-006-20260320
compiler: clang-20
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/202603221745.8279cd80-lkp@intel.com
[ 24.381821][ T56] FDC 0 is a S82078B
[ 24.401375][ T1] brd: module loaded
[ 24.480448][ T1] drbd: initialized. Version: 9.3.0 (api:2/proto:118-123)
[ 24.481932][ T1] drbd: built-in
[ 24.482693][ T1] drbd: registered as block device major 147
[ 24.486081][ T1] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000021: 0000 [#1] KASAN PTI
[ 24.487070][ T1] KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]
[ 24.487070][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 7.0.0-rc4-00020-g945807e66a14 #1 PREEMPT(full) 657bb35ca7e5e0c42c8110b4a9a3d43552818707
[ 24.487070][ T1] Tainted: [T]=RANDSTRUCT
[ 24.487070][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 24.487070][ T1] RIP: 0010:drbd_register_transport_class (kbuild/src/consumer/drivers/block/drbd/drbd_transport.c:44 (discriminator 1027))
[ 24.487070][ T1] Code: c0 00 00 00 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 fa 8d 33 fd 41 bf 08 01 00 00 4c 03 3b 4c 89 f8 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 ff e8 db 8d 33 fd 49 8b 07 48 85 c0 48
All code
========
0: c0 00 00 rolb $0x0,(%rax)
3: 00 48 89 add %cl,-0x77(%rax)
6: d8 48 c1 fmuls -0x3f(%rax)
9: e8 03 42 80 3c call 0x3c804211
e: 28 00 sub %al,(%rax)
10: 74 08 je 0x1a
12: 48 89 df mov %rbx,%rdi
15: e8 fa 8d 33 fd call 0xfffffffffd338e14
1a: 41 bf 08 01 00 00 mov $0x108,%r15d
20: 4c 03 3b add (%rbx),%r15
23: 4c 89 f8 mov %r15,%rax
26: 48 c1 e8 03 shr $0x3,%rax
2a:* 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 ff mov %r15,%rdi
34: e8 db 8d 33 fd call 0xfffffffffd338e14
39: 49 8b 07 mov (%r15),%rax
3c: 48 85 c0 test %rax,%rax
3f: 48 rex.W
Code starting with the faulting instruction
===========================================
0: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1)
5: 74 08 je 0xf
7: 4c 89 ff mov %r15,%rdi
a: e8 db 8d 33 fd call 0xfffffffffd338dea
f: 49 8b 07 mov (%r15),%rax
12: 48 85 c0 test %rax,%rax
15: 48 rex.W
[ 24.487070][ T1] RSP: 0000:ffffc9000001fab0 EFLAGS: 00010206
[ 24.487070][ T1] RAX: 0000000000000021 RBX: ffffffff8a1514a0 RCX: 0000000000000000
[ 24.487070][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 24.487070][ T1] RBP: ffffc9000001fae8 R08: 0000000000000000 R09: 0000000000000000
[ 24.487070][ T1] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff8a1514b0
[ 24.487070][ T1] R13: dffffc0000000000 R14: ffffffff881d2a80 R15: 0000000000000108
[ 24.487070][ T1] FS: 0000000000000000(0000) GS:0000000000000000(0000) knlGS:0000000000000000
[ 24.487070][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 24.487070][ T1] CR2: ffff88883ffff000 CR3: 0000000009438000 CR4: 00000000000406f0
[ 24.487070][ T1] Call Trace:
[ 24.487070][ T1] <TASK>
[ 24.487070][ T1] dtt_initialize (kbuild/src/consumer/drivers/block/drbd/drbd_transport_tcp.c:?)
[ 24.487070][ T1] __initstub__kmod_drbd_transport_tcp__1030_1667_dtt_initialize6 (kbuild/src/consumer/drivers/block/drbd/drbd_transport_tcp.c:1667)
[ 24.487070][ T1] do_one_initcall (kbuild/src/consumer/init/main.c:1382)
[ 24.487070][ T1] ? __cfi___initstub__kmod_drbd_transport_tcp__1030_1667_dtt_initialize6 (kbuild/src/consumer/drivers/block/drbd/drbd_transport_tcp.c:1667)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260322/202603221745.8279cd80-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-22 10:07 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=202603221745.8279cd80-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=christoph.boehmwalder@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--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 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.