INFO: rcu detected stall in write_comp_data
10 views
Skip to first unread message
syzbot
Apr 27, 2020, 3:05:11 AM4/27/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 7edd66cf Linux 4.19.118
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13caa778100000
kernel config: https://syzkaller.appspot.com/x/.config?x=8dd19d0705ec9e0
dashboard link: https://syzkaller.appspot.com/bug?extid=41fa83d5618f0e43984d
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+41fa83...@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device bond451
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (1 GPs behind) idle=2b6/1/0x4000000000000004 softirq=117498/117501 fqs=0
rcu: (t=10500 jiffies g=162797 q=80)
rcu: rcu_preempt kthread starved for 10500 jiffies! g162797 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt R running task 29136 10 2 0x80000000
Call Trace:
schedule+0x8d/0x1b0 kernel/sched/core.c:3559
schedule_timeout+0x4d1/0xf20 kernel/time/timer.c:1806
rcu_gp_kthread+0xcee/0x2060 kernel/rcu/tree.c:2202
kthread+0x34a/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
NMI backtrace for cpu 0
CPU: 0 PID: 1330 Comm: syz-executor.5 Not tainted 4.19.118-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:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:write_comp_data+0x0/0x70 kernel/kcov.c:121
Code: 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 <65> 4c 8b 04 25 40 ee 01 00 65 8b 05 d0 43 9a 7e a9 00 01 1f 00 75
RSP: 0018:ffff8880ae607d38 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 0000000000000100 RCX: ffffffff81587944
RDX: 0000000000000100 RSI: 0000000000000100 RDI: 0000000000000004
RBP: 0000000000000100 R08: 0000000000000000 R09: 0000000000000001
R10: ffffed1015cc4732 R11: ffff8880ae623993 R12: ffff8880ae607d70
R13: 1ffff11015cc0faa R14: 0000000000000000 R15: ffff88803e698010
call_timer_fn+0x1f4/0x700 kernel/time/timer.c:1331
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:skip_atoi+0x82/0xe0 lib/vsprintf.c:130
Code: 48 c1 e8 03 83 e2 07 42 0f b6 04 20 38 d0 7f 04 84 c0 75 4b 0f be 43 ff 48 89 da 83 e2 07 44 8d 74 05 d0 48 89 d8 48 c1 e8 03 <42> 0f b6 04 20 38 d0 7f 04 84 c0 75 2f 0f be 2b bf 09 00 00 00 83
RSP: 0018:ffff888059b0f878 EFLAGS: 00000a02 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff0f1a589 RBX: ffffffff878d2c48 RCX: ffffc90010525000
RDX: 0000000000000000 RSI: ffffffff871b2281 RDI: ffffffff878d2c47
RBP: 000000000000000a R08: ffff88808387e400 R09: ffffed1004016932
R10: ffffed1004016931 R11: ffff8880200b498a R12: dffffc0000000000
R13: ffff888059b0f8e0 R14: 000000000000000a R15: 0000000000000031
format_decode+0x87f/0xad0 lib/vsprintf.c:2062
vsnprintf+0x155/0x14f0 lib/vsprintf.c:2245
seq_vprintf+0xe2/0x1a0 fs/seq_file.c:391
seq_printf+0xbb/0xf0 fs/seq_file.c:406
projid_m_show+0x174/0x220 kernel/user_namespace.c:638
seq_read+0x4b9/0x10f0 fs/seq_file.c:229
do_loop_readv_writev fs/read_write.c:701 [inline]
do_loop_readv_writev fs/read_write.c:688 [inline]
do_iter_read+0x46b/0x640 fs/read_write.c:925
vfs_readv+0xf0/0x160 fs/read_write.c:987
do_preadv+0x1b6/0x270 fs/read_write.c:1071
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:00007f11899d2c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00000000004fa1c0 RCX: 000000000045c829
RDX: 00000000000000f2 RSI: 00000000200017c0 RDI: 0000000000000005
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000085c R14: 00000000004cb1c7 R15: 00007f11899d36d4
netlink: 20 bytes leftover after parsing attributes in process `syz-executor.1'.
---
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 found the following crash on:
HEAD commit: 7edd66cf Linux 4.19.118
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13caa778100000
kernel config: https://syzkaller.appspot.com/x/.config?x=8dd19d0705ec9e0
dashboard link: https://syzkaller.appspot.com/bug?extid=41fa83d5618f0e43984d
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+41fa83...@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device bond451
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (1 GPs behind) idle=2b6/1/0x4000000000000004 softirq=117498/117501 fqs=0
rcu: (t=10500 jiffies g=162797 q=80)
rcu: rcu_preempt kthread starved for 10500 jiffies! g162797 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt R running task 29136 10 2 0x80000000
Call Trace:
schedule+0x8d/0x1b0 kernel/sched/core.c:3559
schedule_timeout+0x4d1/0xf20 kernel/time/timer.c:1806
rcu_gp_kthread+0xcee/0x2060 kernel/rcu/tree.c:2202
kthread+0x34a/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
NMI backtrace for cpu 0
CPU: 0 PID: 1330 Comm: syz-executor.5 Not tainted 4.19.118-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:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:write_comp_data+0x0/0x70 kernel/kcov.c:121
Code: 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 <65> 4c 8b 04 25 40 ee 01 00 65 8b 05 d0 43 9a 7e a9 00 01 1f 00 75
RSP: 0018:ffff8880ae607d38 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 0000000000000100 RCX: ffffffff81587944
RDX: 0000000000000100 RSI: 0000000000000100 RDI: 0000000000000004
RBP: 0000000000000100 R08: 0000000000000000 R09: 0000000000000001
R10: ffffed1015cc4732 R11: ffff8880ae623993 R12: ffff8880ae607d70
R13: 1ffff11015cc0faa R14: 0000000000000000 R15: ffff88803e698010
call_timer_fn+0x1f4/0x700 kernel/time/timer.c:1331
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:skip_atoi+0x82/0xe0 lib/vsprintf.c:130
Code: 48 c1 e8 03 83 e2 07 42 0f b6 04 20 38 d0 7f 04 84 c0 75 4b 0f be 43 ff 48 89 da 83 e2 07 44 8d 74 05 d0 48 89 d8 48 c1 e8 03 <42> 0f b6 04 20 38 d0 7f 04 84 c0 75 2f 0f be 2b bf 09 00 00 00 83
RSP: 0018:ffff888059b0f878 EFLAGS: 00000a02 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff0f1a589 RBX: ffffffff878d2c48 RCX: ffffc90010525000
RDX: 0000000000000000 RSI: ffffffff871b2281 RDI: ffffffff878d2c47
RBP: 000000000000000a R08: ffff88808387e400 R09: ffffed1004016932
R10: ffffed1004016931 R11: ffff8880200b498a R12: dffffc0000000000
R13: ffff888059b0f8e0 R14: 000000000000000a R15: 0000000000000031
format_decode+0x87f/0xad0 lib/vsprintf.c:2062
vsnprintf+0x155/0x14f0 lib/vsprintf.c:2245
seq_vprintf+0xe2/0x1a0 fs/seq_file.c:391
seq_printf+0xbb/0xf0 fs/seq_file.c:406
projid_m_show+0x174/0x220 kernel/user_namespace.c:638
seq_read+0x4b9/0x10f0 fs/seq_file.c:229
do_loop_readv_writev fs/read_write.c:701 [inline]
do_loop_readv_writev fs/read_write.c:688 [inline]
do_iter_read+0x46b/0x640 fs/read_write.c:925
vfs_readv+0xf0/0x160 fs/read_write.c:987
do_preadv+0x1b6/0x270 fs/read_write.c:1071
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:00007f11899d2c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00000000004fa1c0 RCX: 000000000045c829
RDX: 00000000000000f2 RSI: 00000000200017c0 RDI: 0000000000000005
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000085c R14: 00000000004cb1c7 R15: 00007f11899d36d4
netlink: 20 bytes leftover after parsing attributes in process `syz-executor.1'.
---
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
Aug 25, 2020, 3:05:12 AM8/25/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages