From: kernel test robot <oliver.sang@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [jimc:dd-drm-fix-1.0] [dyndbg] d0917089b0: KASAN:maybe_wild-memory-access_in_range[#-#]
Date: Mon, 29 Jun 2026 12:59:34 +0800 [thread overview]
Message-ID: <202606291107.779cbeaf-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6222 bytes --]
hi, Jim Cromie,
the parent also has problems, it crashes after below (1), and this just happens
at the similar position for d0917089b0, which crashes as (2).
one parent dmesg 9ad2106fa015-dmesg.decoded.xz is attached.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb/boot/debian-11.1-i386-20220923.cgz/x86_64-randconfig-072-20260623/gcc-14/1
9ad2106fa015a2fb d0917089b03d3df1f97a2b2b253
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 dmesg.KASAN:maybe_wild-memory-access_in_range[#-#] <------ (2)
6:6 -100% :6 dmesg.KASAN:null-ptr-deref_in_range[#-#] <------ (1)
6:6 0% 6:6 dmesg.Kernel_panic-not_syncing:Fatal_exception
6:6 0% 6:6 dmesg.Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]KASAN
6:6 0% 6:6 dmesg.RIP:strcmp
6:6 0% 6:6 dmesg.boot_failures
not sure if this report could be helpful for the existing issues in this branch
by our boot tests, just report FYI.
Hello,
kernel test robot noticed "KASAN:maybe_wild-memory-access_in_range[#-#]" on:
commit: d0917089b03d3df1f97a2b2b253698012a8a4123 ("dyndbg: drop ->site pointer and compute descs offsets")
https://github.com/jimc/linux.git dd-drm-fix-1.0
in testcase: boot
config: x86_64-randconfig-072-20260623
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/202606291107.779cbeaf-lkp@intel.com
[ 17.795946][ T0] Running RCU synchronous self tests
[ 17.808199][ T1] Performance Events: unsupported CPU family 6 model 42 no PMU driver, software events only.
[ 17.817312][ T1] signal: max sigframe size: 1776
[ 17.827444][ T1] rcu: Hierarchical SRCU implementation.
[ 17.831681][ T1] rcu: Max phase no-delay instances is 1000.
[ 18.750779][ T1] Oops: general protection fault, probably for non-canonical address 0xe007ffe1e0000000: 0000 [#1] KASAN
[ 18.753821][ T1] KASAN: maybe wild-memory-access in range [0x00401f0f00000000-0x00401f0f00000007]
[ 18.753821][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 7.1.0-00060-gd0917089b03d #1 PREEMPT
[ 18.753821][ T1] Tainted: [T]=RANDSTRUCT
[ 18.753821][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 18.753821][ T1] RIP: 0010:strcmp (kbuild/src/lib/string.c:283)
[ 18.753821][ T1] Code: 56 41 55 41 54 55 48 89 fd 53 48 89 f3 49 be 00 00 00 00 00 fc ff df 48 89 ef 48 ff c5 48 89 f8 48 89 fa 48 c1 e8 03 83 e2 07 <42> 8a 04 30 38 d0 7f 09 84 c0 74 05 e8 80 22 70 fa 48 89 d8 48 89
All code
========
0: 56 push %rsi
1: 41 55 push %r13
3: 41 54 push %r12
5: 55 push %rbp
6: 48 89 fd mov %rdi,%rbp
9: 53 push %rbx
a: 48 89 f3 mov %rsi,%rbx
d: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14
14: fc ff df
17: 48 89 ef mov %rbp,%rdi
1a: 48 ff c5 inc %rbp
1d: 48 89 f8 mov %rdi,%rax
20: 48 89 fa mov %rdi,%rdx
23: 48 c1 e8 03 shr $0x3,%rax
27: 83 e2 07 and $0x7,%edx
2a:* 42 8a 04 30 mov (%rax,%r14,1),%al <-- trapping instruction
2e: 38 d0 cmp %dl,%al
30: 7f 09 jg 0x3b
32: 84 c0 test %al,%al
34: 74 05 je 0x3b
36: e8 80 22 70 fa call 0xfffffffffa7022bb
3b: 48 89 d8 mov %rbx,%rax
3e: 48 rex.W
3f: 89 .byte 0x89
Code starting with the faulting instruction
===========================================
0: 42 8a 04 30 mov (%rax,%r14,1),%al
4: 38 d0 cmp %dl,%al
6: 7f 09 jg 0x11
8: 84 c0 test %al,%al
a: 74 05 je 0x11
c: e8 80 22 70 fa call 0xfffffffffa702291
11: 48 89 d8 mov %rbx,%rax
14: 48 rex.W
15: 89 .byte 0x89
[ 18.753821][ T1] RSP: 0000:ffffc9000001fa98 EFLAGS: 00010246
[ 18.753821][ T1] RAX: 000803e1e0000000 RBX: ffffffff87402c60 RCX: 0000000000000000
[ 18.753821][ T1] RDX: 0000000000000000 RSI: ffffffff87402c60 RDI: 00401f0f00000000
[ 18.753821][ T1] RBP: 00401f0f00000001 R08: 0000000000000000 R09: 0000000000000000
[ 18.753821][ T1] R10: 0000000000000000 R11: 0000000000000000 R12: 0000001f8da56e88
[ 18.753821][ T1] R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000000
[ 18.753821][ T1] FS: 0000000000000000(0000) GS:0000000000000000(0000) knlGS:0000000000000000
[ 18.753821][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 18.753821][ T1] CR2: ffff88883ffff000 CR3: 000000000a708000 CR4: 00000000000406b0
[ 18.753821][ T1] Call Trace:
[ 18.753821][ T1] <TASK>
[ 18.753821][ T1] ddebug_add_module (kbuild/src/lib/dynamic_debug.c:1705 (discriminator 8))
[ 18.753821][ T1] ? rcu_read_unlock (kbuild/src/include/linux/rcupdate.h:310 kbuild/src/include/linux/rcupdate.h:869)
[ 18.753821][ T1] ? __lock_release+0x5a/0x150
[ 18.753821][ T1] ? rcu_read_unlock (kbuild/src/include/linux/rcupdate.h:310 kbuild/src/include/linux/rcupdate.h:869)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260629/202606291107.779cbeaf-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: 9ad2106fa015-dmesg.decoded.xz --]
[-- Type: application/x-xz, Size: 7432 bytes --]
reply other threads:[~2026-06-29 4: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=202606291107.779cbeaf-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=jim.cromie@gmail.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ukaszb@chromium.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.