Forwarded: Re: [syzbot] [kernel?] WARNING in get_from_partial_node

Forwarded: Re: [syzbot] [kernel?] WARNING in get_from_partial_node

[syzbot]

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [kernel?] WARNING in get_from_partial_node
Author: koike@igalia.com

#syz test

On 4/14/26 8:20 PM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    1c7cc4904160 Add linux-next specific files for 20260413
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=141b7b02580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f5ee3699e4b6706d
> dashboard link: https://syzkaller.appspot.com/bug?extid=b8ca586b9fc235f0c0df
> compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=152084ce580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=145bd8ce580000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4627c340a79d/disk-1c7cc490.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b1c9e5b70193/vmlinux-1c7cc490.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/8c2cc41fa3d8/bzImage-1c7cc490.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+b8ca586b9fc235f0c0df@syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> debug_locks && !(!get_current()->pi_blocked_on)
> WARNING: kernel/locking/spinlock_rt.c:40 at rtlock_lock kernel/locking/spinlock_rt.c:40 [inline], CPU#0: syz.0.196/6385
> WARNING: kernel/locking/spinlock_rt.c:40 at __rt_spin_lock kernel/locking/spinlock_rt.c:49 [inline], CPU#0: syz.0.196/6385
> WARNING: kernel/locking/spinlock_rt.c:40 at rt_spin_lock+0x31c/0x400 kernel/locking/spinlock_rt.c:57, CPU#0: syz.0.196/6385
> Modules linked in:
> CPU: 0 UID: 0 PID: 6385 Comm: syz.0.196 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
> RIP: 0010:rtlock_lock kernel/locking/spinlock_rt.c:40 [inline]
> RIP: 0010:__rt_spin_lock kernel/locking/spinlock_rt.c:49 [inline]
> RIP: 0010:rt_spin_lock+0x31c/0x400 kernel/locking/spinlock_rt.c:57
> Code: 48 3b 44 24 60 0f 85 98 00 00 00 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 3a 13 f1 f5 e9 ac fe ff ff 90 <0f> 0b 90 e9 f6 fd ff ff 90 0f 0b 90 e9 3f ff ff ff e8 1e 13 f1 f5
> RSP: 0018:ffffc90003d075a0 EFLAGS: 00010282
> RAX: 1ffff1100b5cb917 RBX: 1ffff920007a0eb8 RCX: 0000000000000046
> RDX: 0000000000000000 RSI: ffffffff8dbf888e RDI: ffffffff8bca4960
> RBP: ffffc90003d07660 R08: ffffffff8223c0d4 R09: ffff88813ff51758
> R10: dffffc0000000000 R11: fffffbfff1f9e17f R12: ffff88805ae5c8b8
> R13: dffffc0000000000 R14: ffff88813ff51700 R15: ffffc90003d075e0
> FS:  00007fc677c8e6c0(0000) GS:ffff888125a6b000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007fc6786dedd5 CR3: 0000000040df8000 CR4: 00000000003526f0
> Call Trace:
>   <TASK>
>   spin_lock include/linux/spinlock_rt.h:45 [inline]
>   get_from_partial_node+0x54/0x480 mm/slub.c:3796
>   get_from_partial mm/slub.c:3924 [inline]
>   ___slab_alloc+0xb2/0x670 mm/slub.c:4440
>   __slab_alloc_node mm/slub.c:4510 [inline]
>   slab_alloc_node mm/slub.c:4886 [inline]
>   kmem_cache_alloc_noprof+0xea/0x680 mm/slub.c:4905
>   kmem_alloc_batch lib/debugobjects.c:371 [inline]
>   fill_pool+0x156/0x580 lib/debugobjects.c:420
>   debug_objects_fill_pool+0x97/0xd0 lib/debugobjects.c:742
>   debug_object_assert_init+0x34/0x340 lib/debugobjects.c:1020
>   debug_hrtimer_assert_init kernel/time/hrtimer.c:495 [inline]
>   hrtimer_start_range_ns+0x3f/0xef0 kernel/time/hrtimer.c:1477
>   futex_lock_pi+0x8df/0xb10 kernel/futex/pi.c:1051
>   do_futex+0x292/0x420 kernel/futex/syscalls.c:146
>   __do_sys_futex kernel/futex/syscalls.c:207 [inline]
>   __se_sys_futex+0x3a8/0x450 kernel/futex/syscalls.c:188
>   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>   do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fc67862c819
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fc677c8e028 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
> RAX: ffffffffffffffda RBX: 00007fc6788a5fa0 RCX: 00007fc67862c819
> RDX: 0000000000000002 RSI: 0000000000000006 RDI: 0000200000000280
> RBP: 00007fc6786c2c91 R08: 0000000000000000 R09: 0000000000000002
> R10: 0000200000000b00 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007fc6788a6038 R14: 00007fc6788a5fa0 R15: 00007ffc9abf4698
>   </TASK>
> 
> 
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
> 
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> 
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
> 
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
> 
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
> 
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
> 
> If you want to undo deduplication, reply with:
> #syz undup