syzbot


WARNING in ata_qc_issue

Status: fixed on 2018/03/23 18:14
Reported-by: syzbot+f7b556d1766502a69d85071d2ff08bd87be53d0f@syzkaller.appspotmail.com
Fix commit: 9173e5e80729 libata: remove WARN() for DMA or PIO command without data
First crash: 2439d, last: 2344d
Discussions (7)
Title Replies (including bot) Last reply
[PATCH 3.16 000/410] 3.16.57-rc1 review 426 (426) 2018/11/12 17:42
[PATCH 3.2 000/153] 3.2.102-rc1 review 155 (155) 2018/05/30 22:14
[PATCH 3.18 00/93] 3.18.103-stable review 102 (102) 2018/04/09 08:13
[PATCH 4.4 00/43] 4.4.125-stable review 64 (64) 2018/03/30 23:56
[PATCH 4.15 000/105] 4.15.14-stable review 115 (115) 2018/03/29 00:42
[PATCH 4.9 00/67] 4.9.91-stable review 77 (77) 2018/03/28 19:24
[PATCH 4.14 000/101] 4.14.31-stable review 107 (107) 2018/03/28 18:41

Sample crash report:
WARNING: CPU: 1 PID: 2909 at drivers/ata/libata-core.c:5391 ata_qc_issue+0x519/0xea0 drivers/ata/libata-core.c:5390
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 2909 Comm: syzkaller668320 Not tainted 4.13.0-rc4-next-20170811 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:16 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:52
 panic+0x1e4/0x417 kernel/panic.c:180
 __warn+0x1c4/0x1d9 kernel/panic.c:541
 report_bug+0x211/0x2d0 lib/bug.c:183
 fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:190
 do_trap_no_signal arch/x86/kernel/traps.c:224 [inline]
 do_trap+0x260/0x390 arch/x86/kernel/traps.c:273
 do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:310
 do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:323
 invalid_op+0x1e/0x30 arch/x86/entry/entry_64.S:930
RIP: 0010:ata_qc_issue+0x519/0xea0 drivers/ata/libata-core.c:5390
RSP: 0018:ffff880069de68f8 EFLAGS: 00010097
RAX: ffff88006c840580 RBX: 0000000000000002 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88006b8b2500 RDI: ffff88006b8b0290
RBP: ffff880069de6a10 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: ffffed000d716046 R12: 0000000000000000
R13: ffff88006b8b238c R14: ffff88006b8b01f8 R15: ffff88006b8b0080
 ata_scsi_translate+0x34a/0x5e0 drivers/ata/libata-scsi.c:2023
 __ata_scsi_queuecmd drivers/ata/libata-scsi.c:4325 [inline]
 ata_scsi_queuecmd+0x2ae/0x6b0 drivers/ata/libata-scsi.c:4374
 scsi_dispatch_cmd+0x432/0xb60 drivers/scsi/scsi_lib.c:1686
 scsi_queue_rq+0x155a/0x1e00 drivers/scsi/scsi_lib.c:1962
 blk_mq_dispatch_rq_list+0x8bc/0x1720 block/blk-mq.c:1073
 blk_mq_sched_dispatch_requests+0x752/0xb40 block/blk-mq-sched.c:147
 __blk_mq_run_hw_queue+0x1aa/0x280 block/blk-mq.c:1155
 __blk_mq_delay_run_hw_queue+0x175/0x1b0 block/blk-mq.c:1203
 blk_mq_run_hw_queue+0x1e/0x30 block/blk-mq.c:1224
 blk_mq_sched_insert_request+0x275/0x890 block/blk-mq-sched.c:386
 blk_execute_rq_nowait+0x16d/0x310 block/blk-exec.c:64
 sg_common_write.isra.17+0xf80/0x1c10 drivers/scsi/sg.c:806
 sg_write+0x7a0/0xc90 drivers/scsi/sg.c:677
 __vfs_write+0xef/0x970 fs/read_write.c:468
 vfs_write+0x189/0x510 fs/read_write.c:518
 SYSC_write fs/read_write.c:565 [inline]
 SyS_write+0xef/0x220 fs/read_write.c:557
 entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x439059
RSP: 002b:00007ffe8db065b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 0000000000439059
RDX: 000000000000002a RSI: 0000000020010000 RDI: 0000000000000003
RBP: 0000000000000086 R08: 00000000000000fe R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000401cb0 R14: 0000000000401d40 R15: 0000000000000000
Dumping ftrace buffer:
   (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (35):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/08/12 00:48 linux-next 91dfed74eabc 360f0528 .config console log report syz C ci-upstream-next-kasan-gce
2017/11/14 20:00 linux-next c9b945f2a731 cf38de00 .config console log report skylake-linux-next-kasan-qemu
2017/11/10 08:15 linux-next d9e0e63d9a6f e0a2b195 .config console log report skylake-linux-next-kasan-qemu
2017/11/08 12:41 linux-next 5a3517e009e9 e0a2b195 .config console log report skylake-linux-next-kasan-qemu
2017/11/07 13:11 linux-next 5a3517e009e9 e0a2b195 .config console log report ci-upstream-next-kasan-gce
2017/11/01 00:58 linux-next 36ef71cae353 e511d9f8 .config console log report ci-upstream-next-kasan-gce
2017/10/29 13:52 linux-next 36ef71cae353 e511d9f8 .config console log report ci-upstream-next-kasan-gce
2017/10/29 03:04 linux-next 36ef71cae353 e511d9f8 .config console log report ci-upstream-next-kasan-gce
2017/10/24 11:34 linux-next 36ef71cae353 e511d9f8 .config console log report ci-upstream-next-kasan-gce
2017/09/17 13:52 linux-next 1f183459b514 da1873aa .config console log report skylake-linux-next-kasan-qemu
2017/09/14 15:26 linux-next 31fc38c47623 96b8e399 .config console log report skylake-linux-next-kasan-qemu
2017/09/07 02:48 linux-next e9fcbcd00963 0ed1da4a .config console log report skylake-linux-next-kasan-qemu
2017/09/06 18:54 linux-next e9fcbcd00963 0ed1da4a .config console log report skylake-linux-next-kasan-qemu
2017/08/30 05:24 linux-next 9458bf6edfa8 ed7f9598 .config console log report ci-upstream-next-kasan-gce
2017/08/29 18:46 linux-next 9458bf6edfa8 ed7f9598 .config console log report ci-upstream-next-kasan-gce
2017/08/25 03:26 linux-next 9506597de2cd 3f1aca48 .config console log report ci-upstream-next-kasan-gce
2017/08/24 18:40 linux-next 9506597de2cd 3f1aca48 .config console log report ci-upstream-next-kasan-gce
2017/08/20 14:07 linux-next bb70832dd42b f238fbd4 .config console log report ci-upstream-next-kasan-gce
2017/08/18 20:29 linux-next bb70832dd42b f238fbd4 .config console log report ci-upstream-next-kasan-gce
2017/08/16 09:42 linux-next 5d51332f20b2 f93be584 .config console log report ci-upstream-next-kasan-gce
2017/08/14 14:40 linux-next 91dfed74eabc 6a0246bf .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.