INFO: rcu detected stall in tipc_subscrp_timeout

7 views
Skip to first unread message

syzbot

unread,
Jan 19, 2020, 7:54:09 AM1/19/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c1141b3a Linux 4.14.166
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1357ccc9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a99b4b74c4c01851
dashboard link: https://syzkaller.appspot.com/bug?extid=2ce54e024c87e536f69b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

INFO: rcu_preempt self-detected stall on CPU
0-...: (1 GPs behind) idle=0ee/140000000000002/0 softirq=34625/34630 fqs=0
(t=10500 jiffies g=9313 c=9312 q=65)
rcu_preempt kthread starved for 10500 jiffies! g9313 c9312 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1
rcu_preempt I29776 8 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x7b8/0x1cd0 kernel/sched/core.c:3384
schedule+0x92/0x1c0 kernel/sched/core.c:3428
schedule_timeout+0x43e/0xe10 kernel/time/timer.c:1746
rcu_gp_kthread+0xbf4/0x1ec0 kernel/rcu/tree.c:2255
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
NMI backtrace for cpu 0
CPU: 0 PID: 13257 Comm: kworker/u4:0 Not tainted 4.14.166-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: tipc_rcv tipc_recv_work
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x142/0x197 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x94 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x141/0x189 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:158 [inline]
rcu_dump_cpu_stacks+0x186/0x1d2 kernel/rcu/tree.c:1396
print_cpu_stall kernel/rcu/tree.c:1542 [inline]
check_cpu_stall kernel/rcu/tree.c:1610 [inline]
__rcu_pending kernel/rcu/tree.c:3390 [inline]
rcu_pending kernel/rcu/tree.c:3452 [inline]
rcu_check_callbacks.cold+0x43d/0xd0a kernel/rcu/tree.c:2792
update_process_times+0x31/0x70 kernel/time/timer.c:1590
tick_sched_handle+0x85/0x160 kernel/time/tick-sched.c:161
tick_sched_timer+0x43/0x130 kernel/time/tick-sched.c:1219
__run_hrtimer kernel/time/hrtimer.c:1223 [inline]
__hrtimer_run_queues+0x270/0xbc0 kernel/time/hrtimer.c:1287
hrtimer_interrupt+0x1d8/0x5d0 kernel/time/hrtimer.c:1321
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1075 [inline]
smp_apic_timer_interrupt+0x11c/0x5e0 arch/x86/kernel/apic/apic.c:1100
apic_timer_interrupt+0x96/0xa0 arch/x86/entry/entry_64.S:792
RIP: 0010:native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:61
RSP: 0018:ffff8880aec07c10 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff0fe2d2c RBX: ffff88809bb77808 RCX: 1ffff1101168ada3
RDX: dffffc0000000000 RSI: ffff88808b456cf8 RDI: ffff88808b456c7c
RBP: ffff8880aec07c30 R08: 0000000000000000 R09: ffff88808b456d18
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
R13: 0000000000000286 R14: ffffed1015d85820 R15: ffff88809bb77808
pv_wait arch/x86/include/asm/paravirt.h:679 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:447 [inline]
__pv_queued_spin_lock_slowpath+0x767/0x950 kernel/locking/qspinlock.c:465
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:669 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:52 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:90 [inline]
do_raw_spin_lock+0x19f/0x240 kernel/locking/spinlock_debug.c:113
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x3b/0x50 kernel/locking/spinlock.c:176
spin_lock_bh include/linux/spinlock.h:322 [inline]
tipc_subscrp_timeout+0x57/0x290 net/tipc/subscr.c:141
call_timer_fn+0x161/0x670 kernel/time/timer.c:1279
expire_timers kernel/time/timer.c:1318 [inline]
__run_timers kernel/time/timer.c:1636 [inline]
__run_timers kernel/time/timer.c:1604 [inline]
run_timer_softirq+0x5b7/0x1520 kernel/time/timer.c:1649
__do_softirq+0x244/0x9a0 kernel/softirq.c:288
invoke_softirq kernel/softirq.c:368 [inline]
irq_exit+0x160/0x1b0 kernel/softirq.c:409
exiting_irq arch/x86/include/asm/apic.h:648 [inline]
smp_apic_timer_interrupt+0x146/0x5e0 arch/x86/kernel/apic/apic.c:1102
apic_timer_interrupt+0x96/0xa0 arch/x86/entry/entry_64.S:792
</IRQ>
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:779 [inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x95/0xe0 kernel/locking/spinlock.c:192
RSP: 0018:ffff888061ddfa30 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff0fe2d29 RBX: 0000000000000286 RCX: 1ffff1101168ad99
RDX: dffffc0000000000 RSI: ffff88808b456ca8 RDI: 0000000000000286
RBP: ffff888061ddfa40 R08: ffff88808b456400 R09: ffff88808b456cc8
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff89bf3c48
R13: 0000000000000000 R14: ffffffff89bf3c48 R15: ffff888058059e10
__debug_object_init+0x171/0x8e0 lib/debugobjects.c:380
debug_object_init+0x16/0x20 lib/debugobjects.c:393
debug_timer_init kernel/time/timer.c:687 [inline]
debug_init kernel/time/timer.c:736 [inline]
init_timer_key+0x31/0x300 kernel/time/timer.c:780
tipc_subscrp_subscribe net/tipc/subscr.c:306 [inline]
tipc_subscrb_rcv_cb+0x640/0xa90 net/tipc/subscr.c:338
tipc_receive_from_sock+0x288/0x4e0 net/tipc/server.c:273
tipc_recv_work+0x8a/0x100 net/tipc/server.c:547
process_one_work+0x863/0x1600 kernel/workqueue.c:2114
worker_thread+0x5d9/0x1050 kernel/workqueue.c:2248
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
May 18, 2020, 8:54:09 AM5/18/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages