INFO: rcu detected stall in inet_twsk_put

7 views
Skip to first unread message

syzbot

unread,
May 5, 2020, 11:39:19 AM5/5/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: fdc07232 Linux 4.19.120
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1494a34c100000
kernel config: https://syzkaller.appspot.com/x/.config?x=7848de5371b4200c
dashboard link: https://syzkaller.appspot.com/bug?extid=ba05483927761fb4f0ed
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+ba0548...@syzkaller.appspotmail.com

FAT-fs (loop2): bogus number of reserved sectors
FAT-fs (loop2): Can't find a valid FAT filesystem
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-....: (1 GPs behind) idle=a76/1/0x4000000000000004 softirq=211104/211119 fqs=5211
rcu: (t=10502 jiffies g=192085 q=388066)
NMI backtrace for cpu 1
CPU: 1 PID: 2144 Comm: syz-executor.0 Not tainted 4.19.120-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+0x188/0x20d 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+0x170/0x1bb 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+0x634/0xddc 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+0x42/0x130 kernel/time/tick-sched.c:1278
__run_hrtimer kernel/time/hrtimer.c:1401 [inline]
__hrtimer_run_queues+0x2fc/0xd50 kernel/time/hrtimer.c:1463
hrtimer_interrupt+0x312/0x770 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:893
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:789 [inline]
RIP: 0010:kmem_cache_free+0xa4/0x260 mm/slab.c:3766
Code: e8 31 2f 00 00 84 c0 74 76 41 f7 c4 00 02 00 00 74 4e e8 6f 63 cf ff 48 83 3d 9f dd 34 07 00 0f 84 a8 01 00 00 4c 89 e7 57 9d <0f> 1f 44 00 00 4c 8b 64 24 20 0f 1f 44 00 00 65 8b 05 e6 07 64 7e
RSP: 0018:ffff8880ae707cd0 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000007 RBX: ffff88809f46a418 RCX: 1ffff1100a7261e5
RDX: 0000000000000000 RSI: ffff888053930f08 RDI: 0000000000000282
RBP: ffff8880a685d980 R08: ffff888053930680 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000282
R13: ffffffff85fe45c3 R14: 0000000000000000 R15: ffff88809f46a5f8
inet_twsk_free+0x123/0x180 net/ipv4/inet_timewait_sock.c:72
inet_twsk_put+0x3b/0x50 net/ipv4/inet_timewait_sock.c:79
call_timer_fn+0x177/0x700 kernel/time/timer.c:1326
expire_timers kernel/time/timer.c:1363 [inline]
__run_timers kernel/time/timer.c:1684 [inline]
__run_timers kernel/time/timer.c:1652 [inline]
run_timer_softirq+0x5d0/0x1540 kernel/time/timer.c:1697
__do_softirq+0x26c/0x93c kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x17b/0x1c0 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:893
</IRQ>
RIP: 0010:schedule_debug kernel/sched/core.c:3327 [inline]
RIP: 0010:__schedule+0x10e/0x1d80 kernel/sched/core.c:3437
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 e9 17 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b 5e 18 48 89 da 48 c1 ea 03 80 3c 02 00 <0f> 85 bd 17 00 00 48 81 3b 9d 6e ac 57 0f 85 4b 1c 00 00 65 8b 05
RSP: 0018:ffff8880a0df78a0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: dffffc0000000000 RBX: ffff8880a0df0000 RCX: ffffc90005cc1000
RDX: 1ffff110141be000 RSI: ffffffff8357adc1 RDI: ffff888053930698
RBP: ffff8880a0df7970 R08: ffff888053930680 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 000000000002c280 R14: ffff888053930680 R15: ffff8880ae72c280
preempt_schedule_common+0x4a/0xc0 kernel/sched/core.c:3639
___preempt_schedule+0x16/0x18
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
_raw_spin_unlock_irqrestore+0xb7/0xe0 kernel/locking/spinlock.c:184
try_to_wake_up+0xb0/0xe90 kernel/sched/core.c:2056
wake_up_process kernel/sched/core.c:2124 [inline]
wake_up_q+0x94/0xf0 kernel/sched/core.c:442
futex_wake+0x3f9/0x490 kernel/futex.c:1636
do_futex+0x31f/0x1b80 kernel/futex.c:3714
__do_sys_futex kernel/futex.c:3770 [inline]
__se_sys_futex kernel/futex.c:3738 [inline]
__x64_sys_futex+0x37c/0x4f0 kernel/futex.c:3738
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c829
Code: 0d b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 db b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa532d3ccf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 000000000078bfa8 RCX: 000000000045c829
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 000000000078bfac
RBP: 000000000078bfa0 R08: 0000000000000009 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 000000000078bfac
R13: 00007ffd277dc0cf R14: 00007fa532d3d9c0 R15: 000000000078bfac


---
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,
Sep 2, 2020, 11:40:10 AM9/2/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