INFO: rcu detected stall in inet_twsk_kill

5 views
Skip to first unread message

syzbot

unread,
Jun 23, 2020, 4:34:12 AM6/23/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: b3a99fd3 Linux 4.19.129
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=132a97c9100000
kernel config: https://syzkaller.appspot.com/x/.config?x=afe60417c22a7f7a
dashboard link: https://syzkaller.appspot.com/bug?extid=51203b4cb3fcef5fc47c
compiler: gcc (GCC) 10.1.0-syz 20200507

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+51203b...@syzkaller.appspotmail.com

print_req_error: I/O error, dev loop4, sector 0
print_req_error: I/O error, dev loop4, sector 0
print_req_error: I/O error, dev loop4, sector 0
print_req_error: I/O error, dev loop4, sector 0
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-....: (10498 ticks this GP) idle=f76/1/0x4000000000000004 softirq=544617/544617 fqs=4815
rcu: (t=10500 jiffies g=520377 q=135640)
NMI backtrace for cpu 1
CPU: 1 PID: 32688 Comm: syz-executor.5 Not tainted 4.19.129-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1eb lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline]
rcu_dump_cpu_stacks+0x15f/0x19c kernel/rcu/tree.c:1340
print_cpu_stall kernel/rcu/tree.c:1478 [inline]
check_cpu_stall kernel/rcu/tree.c:1550 [inline]
__rcu_pending kernel/rcu/tree.c:3293 [inline]
rcu_pending kernel/rcu/tree.c:3336 [inline]
rcu_check_callbacks.cold+0x62d/0xe19 kernel/rcu/tree.c:2682
update_process_times+0x2a/0x70 kernel/time/timer.c:1638
tick_sched_handle+0x9b/0x180 kernel/time/tick-sched.c:168
tick_sched_timer+0xfc/0x290 kernel/time/tick-sched.c:1278
__run_hrtimer kernel/time/hrtimer.c:1401 [inline]
__hrtimer_run_queues+0x3f6/0xe60 kernel/time/hrtimer.c:1463
hrtimer_interrupt+0x32a/0x930 kernel/time/hrtimer.c:1521
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1067 [inline]
smp_apic_timer_interrupt+0x10c/0x550 arch/x86/kernel/apic/apic.c:1092
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:894
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:789 [inline]
RIP: 0010:kmem_cache_free+0x11c/0x260 mm/slab.c:3766
Code: 11 48 63 75 74 48 89 df e8 21 14 c1 01 e9 68 ff ff ff e8 a7 53 cf ff 48 83 3d 37 d5 32 07 00 0f 84 f8 00 00 00 4c 89 e7 57 9d <0f> 1f 44 00 00 eb 86 65 8b 05 46 fb 61 7e 83 f8 3f 0f 87 e7 00 00
RSP: 0018:ffff8880ae707c58 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000007 RBX: ffff888085015f00 RCX: 1ffff1100a3f055a
RDX: 0000000000000000 RSI: ffff888051f82ab0 RDI: 0000000000000286
RBP: ffff88821a576980 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000286
R13: ffffffff86147bd2 R14: ffff888085015f00 R15: 000000000000ffff
inet_bind_bucket_destroy net/ipv4/inet_hashtables.c:90 [inline]
inet_bind_bucket_destroy+0xe2/0x120 net/ipv4/inet_hashtables.c:86
inet_twsk_bind_unhash+0x115/0x180 net/ipv4/inet_timewait_sock.c:38
inet_twsk_kill+0x319/0x420 net/ipv4/inet_timewait_sock.c:58
call_timer_fn+0x177/0x700 kernel/time/timer.c:1326
expire_timers+0x243/0x4e0 kernel/time/timer.c:1363
__run_timers kernel/time/timer.c:1684 [inline]
run_timer_softirq+0x21c/0x670 kernel/time/timer.c:1697
__do_softirq+0x26c/0x9a0 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x215/0x260 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:544 [inline]
smp_apic_timer_interrupt+0x136/0x550 arch/x86/kernel/apic/apic.c:1094
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:894
</IRQ>
RIP: 0010:__sanitizer_cov_trace_pc+0x47/0x50 kernel/kcov.c:111
Code: 90 d8 12 00 00 83 fa 02 75 20 48 8b 88 e0 12 00 00 8b 80 dc 12 00 00 48 8b 11 48 83 c2 01 48 39 d0 76 07 48 89 34 d1 48 89 11 <c3> 0f 1f 84 00 00 00 00 00 49 89 f1 49 89 fa 65 48 8b 34 25 40 ee
RSP: 0018:ffff88804f067958 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff888051f82200 RBX: 0000000000055b7b RCX: ffffffff819f3e0c
RDX: 0000000000000000 RSI: ffffffff8185aad9 RDI: 0000000000000001
RBP: ffffea000156dec0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff888055b7b000
R13: 000000000000000a R14: ffffed101504b4b5 R15: ffffea000156dec0
free_pages_prepare mm/page_alloc.c:1059 [inline]
free_pcp_prepare mm/page_alloc.c:1069 [inline]
free_unref_page_prepare+0x1f9/0x5d0 mm/page_alloc.c:2757
free_unref_page+0x20/0x170 mm/page_alloc.c:2806
__vunmap+0x21b/0x3f0 mm/vmalloc.c:1531
vfree+0x65/0x100 mm/vmalloc.c:1598
kcov_put kernel/kcov.c:237 [inline]
kcov_put+0x1f/0x30 kernel/kcov.c:234
kcov_close+0xc/0x10 kernel/kcov.c:323
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
get_signal+0x3f2/0x1f70 kernel/signal.c:2588
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:821
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45ca59
Code: Bad RIP value.
RSP: 002b:00007f3425fbac78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: fffffffffffffff5 RBX: 00000000004dae60 RCX: 000000000045ca59
RDX: 0000000000000048 RSI: 00000000200054c0 RDI: 0000000000000005
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000006f R14: 00000000004c334a R15: 00007f3425fbb6d4


---
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,
Oct 21, 2020, 4:34:12 AM10/21/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