BUG: corrupted list in deadline_remove_request

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: a844dc4c Linux 4.14.158
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15fbac99e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c02bef505ffc02ff
dashboard link: https://syzkaller.appspot.com/bug?extid=ab2fe707b40f6c59acb4
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+ab2fe7...@syzkaller.appspotmail.com

protocol 88fb is buggy, dev hsr_slave_1
protocol 88fb is buggy, dev hsr_slave_0
protocol 88fb is buggy, dev hsr_slave_1
list_del corruption. prev->next should be ffff8880a1a05400, but was
ffff8880a1a07000
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:51!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 2268 Comm: kworker/1:1H Not tainted 4.14.158-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: kblockd blk_mq_run_work_fn
task: ffff8880a38cc040 task.stack: ffff8880a38d8000
RIP: 0010:__list_del_entry_valid.cold+0xf/0x4f lib/list_debug.c:51
RSP: 0018:ffff8880a38dfb58 EFLAGS: 00010282
RAX: 0000000000000054 RBX: ffff8880a1a05400 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86cc43c0 RDI: ffffed101471bf61
RBP: ffff8880a38dfb70 R08: 0000000000000054 R09: ffff8880a38cc958
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880a1a04600
R13: ffff8880a1a06200 R14: ffff8880a1a05400 R15: ffff8880a1a05400
FS: 0000000000000000(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000007176b4 CR3: 0000000007e6a000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del_init include/linux/list.h:159 [inline]
deadline_remove_request+0x6c/0x3f0 block/mq-deadline.c:111
deadline_move_request block/mq-deadline.c:174 [inline]
__dd_dispatch_request block/mq-deadline.c:285 [inline]
dd_dispatch_request+0x54d/0x8d0 block/mq-deadline.c:297
blk_mq_sched_dispatch_requests+0x568/0x810 block/blk-mq-sched.c:143
__blk_mq_run_hw_queue+0x11d/0x320 block/blk-mq.c:1195
blk_mq_run_work_fn+0x78/0xa0 block/blk-mq.c:1396
process_one_work+0x863/0x1600 kernel/workqueue.c:2114
worker_thread+0x5d9/0x1050 kernel/workqueue.c:2248
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 87 e8 a8 8f 40 fe 0f 0b 48 89 f1 48 c7 c7 40 0e 04 87 4c 89 e6 e8 94
8f 40 fe 0f 0b 4c 89 f6 48 c7 c7 e0 0f 04 87 e8 83 8f 40 fe <0f> 0b 4c 89
ea 4c 89 f6 48 c7 c7 20 0f 04 87 e8 6f 8f 40 fe 0f
RIP: __list_del_entry_valid.cold+0xf/0x4f lib/list_debug.c:51 RSP:
ffff8880a38dfb58
---[ end trace 2fd6b1ee27d31aaf ]---


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.