[v6.1] INFO: rcu detected stall in aoecmd_cfg (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 779f9571ac3e Linux 6.1.164
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1479d9e6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=f2dd27d7180fee5ce249
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d8bc7a0c33a8/disk-779f9571.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/870b0bf266c7/vmlinux-779f9571.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ce1e3301c41d/bzImage-779f9571.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f2dd27...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-.... } 2673 jiffies s: 168921 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 26273 Comm: syz.0.7032 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:arch_static_branch arch/x86/include/asm/jump_label.h:27 [inline]
RIP: 0010:static_key_false include/linux/jump_label.h:207 [inline]
RIP: 0010:native_write_msr arch/x86/include/asm/msr.h:147 [inline]
RIP: 0010:wrmsr arch/x86/include/asm/msr.h:254 [inline]
RIP: 0010:native_apic_msr_write+0x35/0x50 arch/x86/include/asm/apic.h:206
Code: 74 2a 83 ff 30 74 25 eb 10 81 ff d0 00 00 00 74 1b 81 ff e0 00 00 00 74 13 c1 ef 04 81 c7 00 08 00 00 89 f9 89 f0 31 d2 0f 30 <66> 90 c3 89 f6 31 d2 e9 ef 48 01 03 66 2e 0f 1f 84 00 00 00 00 00
RSP: 0018:ffffc900001e0370 EFLAGS: 00000046
RAX: 00000000000000b0 RBX: 00000000000000b0 RCX: 0000000000000838
RDX: 0000000000000000 RSI: 00000000000000b0 RDI: 0000000000000838
RBP: 0000000000000000 R08: ffffffff8e1fcd2f R09: 1ffffffff1c3f9a5
R10: dffffc0000000000 R11: fffffbfff1c3f9a6 R12: dffffc0000000000
R13: 00000000100064a9 R14: ffffffff8c64fb40 R15: dffffc0000000000
FS: 00007fef218386c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001620 CR3: 000000007aa9f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000008d24
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
apic_write arch/x86/include/asm/apic.h:394 [inline]
lapic_next_event+0x5b/0x70 arch/x86/kernel/apic/apic.c:478
clockevents_program_event+0x1bc/0x310 kernel/time/clockevents.c:334
hrtimer_interrupt+0x59d/0x9c0 kernel/time/hrtimer.c:1886
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1107 [inline]
__sysvec_apic_timer_interrupt+0x153/0x5a0 arch/x86/kernel/apic/apic.c:1124
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0x4d/0xc0 arch/x86/kernel/apic/apic.c:1118
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:stack_trace_consume_entry+0x1/0x270 kernel/stacktrace.c:83
Code: 00 42 c7 44 33 08 00 00 00 00 65 48 8b 0c 25 28 00 00 00 48 3b 4c 24 78 75 09 48 8d 65 f0 5b 41 5e 5d c3 e8 11 81 bb 08 90 55 <41> 57 41 56 41 55 41 54 53 48 83 ec 18 48 ba 00 00 00 00 00 fc ff
RSP: 0018:ffffc900001e05f8 EFLAGS: 00000286
RAX: ffffffff818ee0ac RBX: ffffc900001e06c0 RCX: 0000000000000100
RDX: ffffc900001e0601 RSI: ffffffff818ee0ac RDI: ffffc900001e06c0
RBP: ffffc900001e0690 R08: ffffc900046b7b58 R09: ffffc900001e0658
R10: dffffc0000000000 R11: fffff5200003c0cd R12: ffff888083230000
R13: 0000000000000000 R14: ffffffff81712460 R15: ffffc900001e0608
arch_stack_walk+0x100/0x140 arch/x86/kernel/stacktrace.c:27
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8e/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:936 [inline]
__kmalloc_node_track_caller+0xae/0x230 mm/slab_common.c:956
kmalloc_reserve net/core/skbuff.c:446 [inline]
__alloc_skb+0x22a/0x7e0 net/core/skbuff.c:515
alloc_skb include/linux/skbuff.h:1271 [inline]
new_skb drivers/block/aoe/aoecmd.c:66 [inline]
aoecmd_cfg_pkts drivers/block/aoe/aoecmd.c:430 [inline]
aoecmd_cfg+0x2c1/0xa40 drivers/block/aoe/aoecmd.c:1374
call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
expire_timers kernel/time/timer.c:1752 [inline]
__run_timers+0x53e/0x800 kernel/time/timer.c:2023
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:unwind_next_frame+0xb80/0x20b0 arch/x86/kernel/unwind_orc.c:546
Code: 3d 9a 00 48 8b 04 24 49 89 06 48 8b 44 24 78 42 0f b6 04 28 84 c0 4c 8b 74 24 10 0f 85 4b 12 00 00 41 c6 07 00 ba 10 00 00 00 <4c> 89 f7 31 f6 e8 36 3e 9a 00 4c 8b 64 24 20 48 8b 3c 24 e9 53 05
RSP: 0018:ffffc900046b70d0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffc900046b71a8 RCX: 1ffff920008d6e01
RDX: 0000000000000010 RSI: ffffffff8e369b70 RDI: ffffc900046b7868
RBP: ffffffff8ea9d6d6 R08: 0000000000000008 R09: 0000000000000006
R10: dffffc0000000000 R11: fffff520008d6e41 R12: 1ffff920008d6e36
R13: dffffc0000000000 R14: ffffc900046b71f8 R15: ffffc900046b71dd
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
save_stack+0x121/0x230 mm/page_owner.c:127
__set_page_owner+0x19/0x60 mm/page_owner.c:190
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2559
prep_new_page mm/page_alloc.c:2566 [inline]
get_page_from_freelist+0x1a1e/0x1ab0 mm/page_alloc.c:4357
__alloc_pages+0x1ec/0x4f0 mm/page_alloc.c:5643
alloc_slab_page+0x5d/0x160 mm/slub.c:1799
allocate_slab mm/slub.c:1944 [inline]
new_slab+0x87/0x2c0 mm/slub.c:1997
___slab_alloc+0xbc6/0x1240 mm/slub.c:3154
__slab_alloc mm/slub.c:3240 [inline]
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x1a0/0x260 mm/slub.c:3398
kmalloc_node_trace+0x22/0xe0 mm/slab_common.c:1039
kmalloc_node include/linux/slab.h:585 [inline]
kzalloc_node include/linux/slab.h:710 [inline]
__get_vm_area_node+0x122/0x330 mm/vmalloc.c:2506
__vmalloc_node_range+0x357/0x13b0 mm/vmalloc.c:3203
__vmalloc_node mm/vmalloc.c:3308 [inline]
__vmalloc+0x76/0x80 mm/vmalloc.c:3322
bpf_prog_alloc_no_stats+0x3a/0x3a0 kernel/bpf/core.c:92
bpf_prog_alloc+0x1c/0x1b0 kernel/bpf/core.c:130
bpf_prog_load+0x7c9/0x1560 kernel/bpf/syscall.c:2597
__sys_bpf+0x5b8/0x780 kernel/bpf/syscall.c:5030
__do_sys_bpf kernel/bpf/syscall.c:5134 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5132 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5132
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fef2099c629
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:00007fef21838028 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fef20c15fa0 RCX: 00007fef2099c629
RDX: 0000000000000048 RSI: 0000200000000200 RDI: 0000000000000005
RBP: 00007fef20a32b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fef20c16038 R14: 00007fef20c15fa0 R15: 00007ffc41b13b58
</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 syzk...@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 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