syzbot

 sign-in | mailing list | source | docs
🐞 Open [717]
🐞 Fixed [181]
🐞 Invalid [640]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

general protection fault in rose_send_frame

Status: upstream: reported C repro on 2019/04/28 12:17
Reported-by: syzbot+b4a4007f9d3479e1f4e2@syzkaller.appspotmail.com
First crash: 2034d, last: 1582d
Fix bisection the fix commit could be any of (bisect log):
  b19ffe6e7205 Linux 4.14.137
  4139fb08c05f Linux 4.14.187
   
▶ ▼ Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 general protection fault in rose_send_frame C done 5 1463d 2041d 1/1 fixed on 2020/12/23 11:20
upstream general protection fault in rose_send_frame (2) hams 7 749d 774d 22/28 fixed on 2023/02/24 13:50
upstream general protection fault in rose_send_frame C done done 664 1462d 2142d 19/28 fixed on 2021/03/10 01:49
▶ ▼ Last patch testing requests (8)
Created Duration User Patch Repo Result
2023/01/28 14:32 15m retest repro linux-4.14.y report log
2023/01/28 12:32 10m retest repro linux-4.14.y report log
2023/01/28 11:32 10m retest repro linux-4.14.y report log
2023/01/28 10:32 10m retest repro linux-4.14.y report log
2022/09/09 15:27 8m retest repro linux-4.14.y report log
2022/09/09 14:27 10m retest repro linux-4.14.y report log
2022/09/09 13:27 9m retest repro linux-4.14.y report log
2022/09/09 12:27 9m retest repro linux-4.14.y report log
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2020/07/01 02:13 29m (2) bisect fix linux-4.14.y OK (2) job log
2020/06/01 00:45 22m bisect fix linux-4.14.y OK (0) job log log
2020/05/02 00:08 24m bisect fix linux-4.14.y OK (0) job log log
2020/04/01 23:34 23m bisect fix linux-4.14.y OK (0) job log log
2020/03/02 23:06 24m bisect fix linux-4.14.y OK (0) job log log
2020/02/01 22:31 23m bisect fix linux-4.14.y OK (0) job log log
2020/01/02 22:01 25m bisect fix linux-4.14.y OK (0) job log log
2019/12/03 21:00 24m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): rose0: link becomes ready
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a987e340 task.stack: ffff8880a9888000
RIP: 0010:rose_send_frame+0x17e/0x250 net/rose/rose_link.c:104
RSP: 0018:ffff8880aeb07b50 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff888215e60840 RCX: 0000000000000006
RDX: 000000000000006b RSI: ffffffff874393e0 RDI: 0000000000000358
RBP: ffff8880a09c7bc0 R08: 0000000000000001 R09: ffff8880a59e4340
R10: ffff8880a59e4363 R11: 0000000000000000 R12: ffff888215e60840
R13: 0000000000000078 R14: 0000000000000000 R15: 0000000000000010
FS:  0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000190 CR3: 00000000a7c6a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 rose_transmit_clear_request+0x1d1/0x280 net/rose/rose_link.c:258
 rose_rx_call_request+0x3c8/0x1813 net/rose/af_rose.c:1000
 rose_loopback_timer+0x13e/0x420 net/rose/rose_loopback.c:103
 call_timer_fn+0x14a/0x650 kernel/time/timer.c:1279
 expire_timers+0x232/0x4d0 kernel/time/timer.c:1318
 __run_timers kernel/time/timer.c:1636 [inline]
 run_timer_softirq+0x1d5/0x5a0 kernel/time/timer.c:1649
 __do_softirq+0x254/0xa1d kernel/softirq.c:288
 invoke_softirq kernel/softirq.c:368 [inline]
 irq_exit+0x193/0x240 kernel/softirq.c:409
 exiting_irq arch/x86/include/asm/apic.h:648 [inline]
 smp_apic_timer_interrupt+0x141/0x5e0 arch/x86/kernel/apic/apic.c:1102
 apic_timer_interrupt+0x93/0xa0 arch/x86/entry/entry_64.S:793
 </IRQ>
RIP: 0010:native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:61
RSP: 0018:ffff8880a988fea8 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff0fa2d24 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000001 RDI: ffff8880a987ebc4
RBP: ffffffff87d16910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffed101530fc68
R13: ffff8880a987e340 R14: 0000000000000000 R15: 0000000000000000
 arch_safe_halt arch/x86/include/asm/paravirt.h:94 [inline]
 default_idle+0x47/0x370 arch/x86/kernel/process.c:558
 cpuidle_idle_call kernel/sched/idle.c:156 [inline]
 do_idle+0x250/0x3c0 kernel/sched/idle.c:246
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:351
 start_secondary+0x488/0x5f0 arch/x86/kernel/smpboot.c:272
 secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 9e 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 73 20 49 8d be 58 03 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 75 4d 8b be 58 03 00 00 e9 cf fe ff ff e8 6b 89 
RIP: rose_send_frame+0x17e/0x250 net/rose/rose_link.c:104 RSP: ffff8880aeb07b50
---[ end trace 1e66e418c23e38a1 ]---

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/07/23 05:31 linux-4.14.y 69b94dd6dcd1 340ea530 .config console log report syz C ci2-linux-4-14
2019/08/09 16:25 linux-4.14.y b19ffe6e7205 aff9e255 .config console log report syz C ci2-linux-4-14
2019/07/21 03:48 linux-4.14.y aea8526edf59 1656845f .config console log report syz C ci2-linux-4-14
2019/04/28 11:16 linux-4.14.y fa5941f45d7e b617407b .config console log report syz C ci2-linux-4-14
2019/07/30 12:48 linux-4.14.y ff33472c282e f28bf2a5 .config console log report ci2-linux-4-14
2019/07/24 23:46 linux-4.14.y ff33472c282e 32329ceb .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.