syzbot


general protection fault in perf_trace_block_get_rq

Status: fixed on 2017/10/24 06:54
Fix commit: f8e9ec16611b block: tolerate tracing of NULL bio
First crash: 2417d, last: 2406d

Sample crash report:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
   (ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 2983 Comm: syzkaller401111 Not tainted 4.13.0-rc7-next-20170901+ #13
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8801cf1da000 task.stack: ffff8801ce440000
RIP: 0010:perf_trace_block_get_rq+0x697/0x970 include/trace/events/block.h:384
RSP: 0018:ffff8801ce4473f0 EFLAGS: 00010246
RAX: ffff8801cf1da000 RBX: 1ffff10039c88e84 RCX: 1ffffd1ffff84d27
RDX: dffffc0000000001 RSI: 1ffff1003b643e7a RDI: ffffe8ffffc26938
RBP: ffff8801ce447530 R08: 1ffff1003b643e6c R09: ffffe8ffffc26964
R10: 0000000000000002 R11: fffff91ffff84d2d R12: ffffe8ffffc1f890
R13: ffffe8ffffc26930 R14: ffffffff85cad9e0 R15: 0000000000000000
FS:  0000000002641880(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000043e670 CR3: 00000001d1d7a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 trace_block_getrq include/trace/events/block.h:423 [inline]
 __get_request block/blk-core.c:1283 [inline]
 get_request+0x1518/0x23b0 block/blk-core.c:1355
 blk_old_get_request block/blk-core.c:1402 [inline]
 blk_get_request+0x1d8/0x3c0 block/blk-core.c:1427
 sg_scsi_ioctl+0x117/0x750 block/scsi_ioctl.c:451
 sg_ioctl+0x192d/0x2ed0 drivers/scsi/sg.c:1070
 vfs_ioctl fs/ioctl.c:45 [inline]
 do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:685
 SYSC_ioctl fs/ioctl.c:700 [inline]
 SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
 entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x443e59
RSP: 002b:00007ffd187a70b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006d4d80 RCX: 0000000000443e59
RDX: 0000000020001000 RSI: 0000000100000001 RDI: 0000000000000004
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000020000
R13: 0000080000000000 R14: 0000000000000000 R15: 0000000000000000
Code: df 48 89 f9 48 c1 e9 03 0f b6 14 11 84 d2 74 09 80 fa 03 0f 8e e1 02 00 00 48 ba 01 00 00 00 00 fc ff df 41 c7 45 08 00 00 00 00 <80> 3a 00 0f 85 b7 02 00 00 4c 8b 3c 25 08 00 00 00 48 ba 00 00 
RIP: perf_trace_block_get_rq+0x697/0x970 include/trace/events/block.h:384 RSP: ffff8801ce4473f0
---[ end trace 7548f150518d0a21 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
   (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (180):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/09/03 18:02 linux-next 1d53d908b79d a54dce00 .config console log report syz C ci-upstream-next-kasan-gce
2017/09/03 17:46 linux-next 1d53d908b79d a54dce00 .config console log report syz C ci-upstream-next-kasan-gce
2017/09/08 06:49 upstream 8dc5b3a6cb2f 0ed1da4a .config console log report ci-upstream-kasan-gce
2017/09/14 02:43 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/14 00:26 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/14 00:22 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 20:29 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 18:35 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 17:47 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 16:56 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 16:17 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 14:23 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 13:26 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 10:26 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 08:58 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 08:18 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 07:06 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 05:38 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 05:29 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 05:08 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/13 04:45 linux-next 6f20b7a58cb9 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/03 17:39 linux-next 1d53d908b79d a54dce00 .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.