[v6.1] INFO: rcu detected stall in ieee80211_tasklet_handler

0 views
Skip to first unread message

syzbot

unread,
Jun 3, 2024, 4:38:25 AMJun 3
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1669a6ba980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=6f03b716fb4541a51f32
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1bcd0657273/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46b8776e602b/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2b8c04da7a29/bzImage-88690811.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 3644 jiffies s: 4841 root: 0x1/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5232 Comm: syz-executor.1 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:sched_clock_cpu+0xac/0x2b0 kernel/sched/clock.c:384
Code: e0 45 4b c7 44 35 00 00 00 00 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 80 00 00 00 0f 85 82 00 00 00 48 89 d8 48 8d 65 d8 5b <41> 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 89 fb 65 ff 05 74 4a
RSP: 0018:ffffc900000075b8 EFLAGS: 00000046
RAX: 00000033a8e24aa3 RBX: ffffffff8d1c0f28 RCX: 1ffffffff1fd3e00
RDX: 1ffffffff1fd3e00 RSI: ffffffff8fe9f01c RDI: ffffffff8fe9f01d
RBP: ffffc900000075d8 R08: ffffffff8fe9f000 R09: ffffffff8fe9f008
R10: ffffffff8fe9f018 R11: ffffffff8fe9f010 R12: ffffc90000007560
R13: dffffc0000000000 R14: 1ffff92000000ea8 R15: ffff888013e8e060
FS: 00007fdce48e16c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c53d000 CR3: 0000000064720000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
local_clock include/linux/sched/clock.h:84 [inline]
cpu_clock_event_update kernel/events/core.c:10908 [inline]
cpu_clock_event_read+0x17/0x50 kernel/events/core.c:10941
perf_swevent_hrtimer+0x115/0x4f0 kernel/events/core.c:10824
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5a7/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x3e/0xb0 arch/x86/kernel/apic/apic.c:1106
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:skb_release_head_state+0x0/0x230 net/core/skbuff.c:839
Code: f9 e9 60 ff ff ff e8 2f 9b 10 f9 44 89 e6 48 c7 c7 80 be 28 8e e8 b0 95 e9 fb e9 cd fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 <55> 41 57 41 56 41 54 53 49 89 fe 49 bc 00 00 00 00 00 fc ff df e8
RSP: 0018:ffffc90000007b90 EFLAGS: 00000246
RAX: ffffffff887a13ec RBX: ffff888077e69dc0 RCX: ffff888013e85940
RDX: 0000000000000101 RSI: ffffffff8b3d45c0 RDI: ffff888077e69dc0
RBP: 0000000000000001 R08: ffffffff887a13d9 R09: fffffbfff1ce712e
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000000f7c
R13: ffffc90000007c00 R14: ffff888077e69ea4 R15: dffffc0000000000
skb_release_all net/core/skbuff.c:854 [inline]
__kfree_skb net/core/skbuff.c:870 [inline]
consume_skb+0x72/0x140 net/core/skbuff.c:1035
ieee80211_tx_status+0x244/0x320 net/mac80211/status.c:1100
ieee80211_tasklet_handler+0x142/0x1b0 net/mac80211/main.c:319
tasklet_action_common+0x3cb/0x4a0
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
invoke_softirq kernel/softirq.c:445 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:650
irq_exit_rcu+0x5/0x20 kernel/softirq.c:662
sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:preempt_schedule_irq+0xf2/0x1c0 kernel/sched/core.c:6870
Code: 89 f5 49 c1 ed 03 eb 0d 48 f7 03 08 00 00 00 0f 84 97 00 00 00 bf 01 00 00 00 e8 f9 c3 ca f6 e8 44 c1 fd f6 fb bf 01 00 00 00 <e8> 99 b4 ff ff 43 80 7c 3d 00 00 74 08 4c 89 f7 e8 d9 7e 4e f7 48
RSP: 0018:ffffc90003b1eba0 EFLAGS: 00000286
RAX: b0209c0febda6d00 RBX: 1ffff92000763d7c RCX: ffffffff91c94103
RDX: dffffc0000000000 RSI: ffffffff8aec01c0 RDI: 0000000000000001
RBP: ffffc90003b1ec50 R08: ffffffff8fe9f000 R09: ffffffff8fe9f008
R10: ffffffff8fe9f018 R11: ffffffff8fe9f010 R12: 1ffff92000763d74
R13: 1ffff92000763d78 R14: ffffc90003b1ebc0 R15: dffffc0000000000
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:put_cpu_partial+0x1af/0x250 mm/slub.c:2661
Code: 3b 44 24 18 0f 85 b4 00 00 00 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 9d 7a a9 08 f7 c3 00 02 00 00 74 c0 fb 4d 85 e4 <75> bf eb c8 e8 48 8e 53 02 85 c0 0f 84 e9 fe ff ff 83 3d 81 30 92
RSP: 0018:ffffc90003b1ed10 EFLAGS: 00000246
RAX: b0209c0febda6d00 RBX: 0000000000000282 RCX: ffffffff91c94103
RDX: dffffc0000000000 RSI: ffffffff8aec01c0 RDI: ffffffff8b3d45e0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ce712e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffffea0001f16980 R14: ffff888013e85940 R15: ffff888140009a00
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0x76/0xe0 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x156/0x170 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x1f/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
__kmem_cache_alloc_node+0x137/0x260 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:954 [inline]
__kmalloc_node_track_caller+0xa0/0x220 mm/slab_common.c:975
__do_krealloc mm/slab_common.c:1348 [inline]
krealloc+0x61/0xf0 mm/slab_common.c:1381
push_jmp_history kernel/bpf/verifier.c:2542 [inline]
is_state_visited kernel/bpf/verifier.c:12387 [inline]
do_check kernel/bpf/verifier.c:12527 [inline]
do_check_common+0x325e/0xc1d0 kernel/bpf/verifier.c:15005
do_check_main kernel/bpf/verifier.c:15068 [inline]
bpf_check+0x1039b/0x15ea0 kernel/bpf/verifier.c:15645
bpf_prog_load+0x12df/0x1bb0 kernel/bpf/syscall.c:2631
__sys_bpf+0x382/0x6c0 kernel/bpf/syscall.c:5005
__do_sys_bpf kernel/bpf/syscall.c:5109 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5107 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5107
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdce3a7cee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdce48e10c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fdce3bb3fa0 RCX: 00007fdce3a7cee9
RDX: 0000000000000090 RSI: 0000000020000200 RDI: 0000000000000005
RBP: 00007fdce3ac947f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fdce3bb3fa0 R15: 00007ffc139e4b98
</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
Reply all
Reply to author
Forward
0 new messages