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

0 views
Skip to first unread message

syzbot

unread,
Jun 4, 2024, 10:31:26 AMJun 4
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=11e6a94a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=07b6b1dd6376c8d6cf9a
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/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 8838 jiffies s: 3357 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: 15 Comm: ksoftirqd/0 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:timerqueue_add+0x11/0x280 lib/timerqueue.c:36
Code: 89 df e8 22 d4 5c f7 e9 84 fc ff ff cc cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 48 83 ec 30 49 89 f7 <49> 89 fc 48 bb 00 00 00 00 00 fc ff df e8 9d 54 05 f7 4c 89 fd 48
RSP: 0018:ffffc90000007cc0 EFLAGS: 00000086
RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000001
RDX: 0000000000010302 RSI: ffff88802360b340 RDI: ffff8880b982a610
RBP: ffff8880b982a504 R08: ffffffff8179e7eb R09: fffffbfff1ce712e
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880b982a610 R14: ffff88802360b340 R15: ffff88802360b340
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020007038 CR3: 000000000ce8e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
enqueue_hrtimer+0x1bd/0x410 kernel/time/hrtimer.c:1092
__run_hrtimer kernel/time/hrtimer.c:1703 [inline]
__hrtimer_run_queues+0x728/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+0x8c/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:unwind_next_frame+0x1/0x2220 arch/x86/kernel/unwind_orc.c:423
Code: 02 31 c0 5b 41 5e 41 5f c3 44 89 f1 80 e1 07 80 c1 03 38 c1 7c 95 4c 89 f7 e8 1b 69 a5 00 eb 8b 66 0f 1f 84 00 00 00 00 00 55 <41> 57 41 56 41 55 41 54 53 48 81 ec a8 00 00 00 48 89 fb 49 be 00
RSP: 0018:ffffc90000146d50 EFLAGS: 00000202
RAX: 0000000000000001 RBX: ffffc90000146d60 RCX: ffffffff8fb12000
RDX: dffffc0000000000 RSI: ffffffff891a72da RDI: ffffc90000146d60
RBP: ffffc90000146df0 R08: 0000000000000005 R09: ffffc90000146e50
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88813fed3b80
R13: ffffffff81784820 R14: ffffc90000146e40 R15: 0000000000000000
arch_stack_walk+0x10d/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
____kasan_kmalloc mm/kasan/common.c:374 [inline]
__kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:383
kmalloc include/linux/slab.h:556 [inline]
ip_setup_cork+0x52f/0x860 net/ipv4/ip_output.c:1283
ip_append_data+0x155/0x1a0 net/ipv4/ip_output.c:1336
icmp_push_reply+0x97/0x410 net/ipv4/icmp.c:368
__icmp_send+0xffa/0x1530 net/ipv4/icmp.c:768
icmp_send include/net/icmp.h:43 [inline]
ip_protocol_deliver_rcu+0x6a7/0x740 net/ipv4/ip_input.c:216
ip_local_deliver_finish+0x304/0x580 net/ipv4/ip_input.c:233
NF_HOOK+0x39d/0x450 include/linux/netfilter.h:302
NF_HOOK+0x39d/0x450 include/linux/netfilter.h:302
__netif_receive_skb_one_core net/core/dev.c:5528 [inline]
__netif_receive_skb+0x1c6/0x530 net/core/dev.c:5642
process_backlog+0x381/0x760 net/core/dev.c:5970
__napi_poll+0xc7/0x470 net/core/dev.c:6537
napi_poll net/core/dev.c:6604 [inline]
net_rx_action+0x70f/0xeb0 net/core/dev.c:6718
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x52c/0xa30 kernel/smpboot.c:164
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 GPs behind) idle=e434/1/0x4000000000000000 softirq=10637/10638 fqs=20
(detected by 1, t=10504 jiffies, g=11457, q=965 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:lock_acquire+0x1/0x5a0 kernel/locking/lockdep.c:5630
Code: fd ff ff 48 c7 c7 28 be 73 8e e8 da ab 77 00 e9 a2 fd ff ff 0f 1f 44 00 00 65 8b 05 51 0e 98 7e a9 00 ff ff 00 0f 95 c0 c3 55 <48> 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0 48 81 ec 20 01 00
RSP: 0018:ffffc90000007c28 EFLAGS: 00000046
RAX: 0000000000010303 RBX: 1ffff92000000f8c RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff91ee17e0
RBP: ffffc90000007cd0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000046
R13: 1ffff92000000f88 R14: ffffffff91ee17c8 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020007038 CR3: 000000000ce8e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
debug_object_deactivate+0x63/0x380 lib/debugobjects.c:752
debug_hrtimer_deactivate kernel/time/hrtimer.c:425 [inline]
debug_deactivate+0x1d/0x280 kernel/time/hrtimer.c:481
__run_hrtimer kernel/time/hrtimer.c:1654 [inline]
__hrtimer_run_queues+0x334/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+0x8c/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:unwind_next_frame+0x1/0x2220 arch/x86/kernel/unwind_orc.c:423
Code: 02 31 c0 5b 41 5e 41 5f c3 44 89 f1 80 e1 07 80 c1 03 38 c1 7c 95 4c 89 f7 e8 1b 69 a5 00 eb 8b 66 0f 1f 84 00 00 00 00 00 55 <41> 57 41 56 41 55 41 54 53 48 81 ec a8 00 00 00 48 89 fb 49 be 00
RSP: 0018:ffffc90000146d50 EFLAGS: 00000202
RAX: 0000000000000001 RBX: ffffc90000146d60 RCX: ffffffff8fb12000
RDX: dffffc0000000000 RSI: ffffffff891a72da RDI: ffffc90000146d60
RBP: ffffc90000146df0 R08: 0000000000000005 R09: ffffc90000146e50
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88813fed3b80
R13: ffffffff81784820 R14: ffffc90000146e40 R15: 0000000000000000
arch_stack_walk+0x10d/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52


---
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