Hello,
syzbot found the following crash on:
HEAD commit: f02af7b0 Merge 4.14.143 into android-4.14
git tree: android-4.14
console output:
https://syzkaller.appspot.com/x/log.txt?x=1177611a600000
kernel config:
https://syzkaller.appspot.com/x/.config?x=4d9cf2fd50fd7015
dashboard link:
https://syzkaller.appspot.com/bug?extid=c495217ceabb212ffa88
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+c49521...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5111 at net/ipv4/tcp_timer.c:429
tcp_retransmit_timer+0x1a66/0x2590 net/ipv4/tcp_timer.c:429
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 5111 Comm: syz-executor.5 Not tainted 4.14.143+ #0
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xca/0x134 lib/dump_stack.c:53
panic+0x1ea/0x3d3 kernel/panic.c:182
__warn.cold+0x2f/0x3a kernel/panic.c:546
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x1bf/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x18/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:tcp_retransmit_timer+0x1a66/0x2590 net/ipv4/tcp_timer.c:429
RSP: 0018:ffff8881dbb07c78 EFLAGS: 00010206
RAX: ffff88819eb29780 RBX: ffff8881a2fa9d80 RCX: 0000000000000001
RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffff8881d322f7c8
RBP: ffff8881d322ee00 R08: ffff88821fffd05c R09: ffff88821fffd048
R10: ffff88821fffd057 R11: ffff88821fffd050 R12: ffff8881d322f49a
R13: ffff8881d322ee30 R14: 0000000000000000 R15: ffff8881d322f60c
tcp_write_timer_handler+0x43d/0x780 net/ipv4/tcp_timer.c:579
tcp_write_timer+0xc9/0x170 net/ipv4/tcp_timer.c:597
call_timer_fn+0x15b/0x6a0 kernel/time/timer.c:1279
expire_timers+0x227/0x4c0 kernel/time/timer.c:1318
__run_timers kernel/time/timer.c:1634 [inline]
run_timer_softirq+0x1eb/0x5d0 kernel/time/timer.c:1647
__do_softirq+0x234/0x9ec kernel/softirq.c:288
invoke_softirq kernel/softirq.c:368 [inline]
irq_exit+0x114/0x150 kernel/softirq.c:409
exiting_irq arch/x86/include/asm/apic.h:648 [inline]
smp_apic_timer_interrupt+0x1a7/0x650 arch/x86/kernel/apic/apic.c:1102
apic_timer_interrupt+0x8c/0xa0 arch/x86/entry/entry_64.S:792
</IRQ>
RIP: 0010:put_dec_trunc8+0x1dd/0x2c0 lib/vsprintf.c:218
RSP: 0018:ffff88819e2277a8 EFLAGS: 00000a02 ORIG_RAX: ffffffffffffff10
RAX: dffffc0000000000 RBX: ffff88819e2277fc RCX: 0000000000040000
RDX: 0000000000000000 RSI: ffffc900000e6000 RDI: ffffffff864e8522
RBP: 0000000000000001 R08: ffff8881c7dfc008 R09: ffffed10394ed00b
R10: ffffed10394ed00a R11: ffff8881ca768050 R12: 0000000000000001
R13: 0000000000000001 R14: 1ffff11033c44efb R15: 0000000000003a82
num_to_str+0x126/0x1dd lib/vsprintf.c:351
seq_put_decimal_ull+0x1af/0x240 fs/seq_file.c:706
do_task_stat+0xb96/0x1b70 fs/proc/array.c:545
proc_single_show+0xf1/0x160 fs/proc/base.c:762
seq_read+0x4f7/0x1180 fs/seq_file.c:237
do_loop_readv_writev fs/read_write.c:699 [inline]
do_loop_readv_writev fs/read_write.c:686 [inline]
do_iter_read+0x3e8/0x5b0 fs/read_write.c:923
vfs_readv+0xe6/0x150 fs/read_write.c:985
do_preadv+0x189/0x230 fs/read_write.c:1069
do_syscall_64+0x19b/0x520 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4598e9
RSP: 002b:00007f8cb5d86c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00000000004598e9
RDX: 0000000000000199 RSI: 00000000200017c0 RDI: 0000000000000005
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8cb5d876d4
R13: 00000000004c6bd1 R14: 00000000004dbe08 R15: 00000000ffffffff
Kernel Offset: 0x3400000 from 0xffffffff81000000 (relocation range:
0xffffffff80000000-0xffffffffbfffffff)
Rebooting in 86400 seconds..
---
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.