syzbot


INFO: task hung in blk_mq_freeze_queue_wait

Status: closed as dup on 2017/12/12 16:51
Reported-by: syzbot+caffa2697ebe6d891ac5d7701d58644a307c470a@syzkaller.appspotmail.com
First crash: 1892d, last: 1825d
Duplicate of (1):
Title Repro Cause bisect Fix bisect Count Last Reported
INFO: task hung in lo_ioctl 47 1767d 1883d
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-49 INFO: task hung in blk_mq_freeze_queue_wait 805 1826d 1887d 0/3 auto-closed as invalid on 2019/02/22 12:49
android-44 INFO: task hung in blk_mq_freeze_queue_wait 92 1829d 1884d 0/2 auto-closed as invalid on 2019/02/22 15:22

Sample crash report:
kworker/dying (8562) used greatest stack depth: 9952 bytes left
INFO: task syz-executor2:2470 blocked for more than 120 seconds.
      Not tainted 4.15.0+ #299
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor2   D23056  2470   4223 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2845 [inline]
 __schedule+0x8eb/0x2060 kernel/sched/core.c:3421
 schedule+0xf5/0x430 kernel/sched/core.c:3480
 blk_mq_freeze_queue_wait+0x1bb/0x400 block/blk-mq.c:136
 blk_freeze_queue+0x4a/0x80 block/blk-mq.c:165
 blk_mq_freeze_queue+0x15/0x20 block/blk-mq.c:174
 loop_change_fd drivers/block/loop.c:667 [inline]
 lo_ioctl+0x10ce/0x1b70 drivers/block/loop.c:1361
 __blkdev_driver_ioctl block/ioctl.c:303 [inline]
 blkdev_ioctl+0x1759/0x1e00 block/ioctl.c:601
 block_ioctl+0xde/0x120 fs/block_dev.c:1860
 vfs_ioctl fs/ioctl.c:46 [inline]
 do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:686
 SYSC_ioctl fs/ioctl.c:701 [inline]
 SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
 do_syscall_64+0x282/0x940 arch/x86/entry/common.c:287
 entry_SYSCALL_64_after_hwframe+0x26/0x9b
RIP: 0033:0x453299
RSP: 002b:00007f1bccc70c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000071bea0 RCX: 0000000000453299
RDX: 0000000000000014 RSI: 0000000000004c06 RDI: 0000000000000014
RBP: 0000000000000265 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006f2a18
R13: 00000000ffffffff R14: 00007f1bccc716d4 R15: 0000000000000000

Showing all locks held in the system:
2 locks held by khungtaskd/754:
 #0:  (rcu_read_lock){....}, at: [<000000003340968f>] check_hung_uninterruptible_tasks kernel/hung_task.c:175 [inline]
 #0:  (rcu_read_lock){....}, at: [<000000003340968f>] watchdog+0x1c5/0xd60 kernel/hung_task.c:249
 #1:  (tasklist_lock){.+.+}, at: [<00000000a7a8eddb>] debug_show_all_locks+0xd3/0x3d0 kernel/locking/lockdep.c:4470
1 lock held by rsyslogd/4020:
 #0:  (&f->f_pos_lock){+.+.}, at: [<00000000cdb0545b>] __fdget_pos+0x12b/0x190 fs/file.c:765
2 locks held by getty/4143:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4144:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4145:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4146:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4147:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4148:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/4149:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000efc3030e>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000204d5db5>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
1 lock held by syz-executor2/2470:
 #0:  (&lo->lo_ctl_mutex/1){+.+.}, at: [<0000000067b0e03c>] lo_ioctl+0x8b/0x1b70 drivers/block/loop.c:1355
1 lock held by blkid/2488:
 #0:  (&lo->lo_ctl_mutex/1){+.+.}, at: [<0000000067b0e03c>] lo_ioctl+0x8b/0x1b70 drivers/block/loop.c:1355

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 754 Comm: khungtaskd Not tainted 4.15.0+ #299
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:53
 nmi_cpu_backtrace+0x1d2/0x210 lib/nmi_backtrace.c:103
 nmi_trigger_cpumask_backtrace+0x122/0x180 lib/nmi_backtrace.c:62
 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
 trigger_all_cpu_backtrace include/linux/nmi.h:138 [inline]
 check_hung_task kernel/hung_task.c:132 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline]
 watchdog+0x90c/0xd60 kernel/hung_task.c:249
 kthread+0x33c/0x400 kernel/kthread.c:238
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:429
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:54

Crashes (608):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce 2018/02/06 12:25 upstream e237f98a9c13 a1bc9d40 .config console log report
ci-upstream-kasan-gce 2018/02/06 12:06 upstream e237f98a9c13 a1bc9d40 .config console log report
ci-upstream-kasan-gce 2018/02/06 11:43 upstream e237f98a9c13 a1bc9d40 .config console log report
ci-upstream-kasan-gce 2018/02/06 08:34 upstream 2deb41b24532 a1bc9d40 .config console log report
ci-upstream-kasan-gce 2018/02/02 21:24 upstream 03f51d4efa22 632a8c2c .config console log report
ci-upstream-kasan-gce 2018/02/02 06:36 upstream 4bf772b14675 826b35d6 .config console log report
ci-upstream-kasan-gce 2018/02/01 02:07 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 23:40 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 21:45 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 17:57 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 16:18 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 15:06 upstream 3da90b159b14 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 10:55 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 10:37 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 10:11 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 09:30 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 09:21 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/31 04:47 upstream 72906f38934a 02553e22 .config console log report
ci-upstream-kasan-gce 2018/01/30 21:49 upstream 72906f38934a a899be78 .config console log report
ci-upstream-kasan-gce 2018/01/30 20:37 upstream 6304672b7f0a a899be78 .config console log report
ci-upstream-kasan-gce 2018/01/30 20:10 upstream 6304672b7f0a a899be78 .config console log report
ci-upstream-kasan-gce 2018/01/29 16:15 upstream d8a5b80568a9 08d47756 .config console log report
ci-upstream-kasan-gce 2018/01/29 03:19 upstream 24b1cccf9229 08d47756 .config console log report
ci-upstream-kasan-gce 2018/01/28 22:26 upstream 24b1cccf9229 08d47756 .config console log report
ci-upstream-kasan-gce 2018/01/28 09:19 upstream c4e0ca7fa241 08d47756 .config console log report
ci-upstream-kasan-gce 2018/01/28 05:03 upstream c4e0ca7fa241 08146b1a .config console log report
ci-upstream-kasan-gce 2018/01/25 08:04 upstream 5132ede0fe80 866f1102 .config console log report
ci-upstream-kasan-gce 2018/01/24 14:07 upstream 1f07476ec143 a5b7566c .config console log report
ci-upstream-kasan-gce 2018/01/24 07:15 upstream 1f07476ec143 a5b7566c .config console log report
ci-upstream-kasan-gce 2018/01/24 06:51 upstream 1f07476ec143 a5b7566c .config console log report
ci-upstream-kasan-gce 2018/01/24 06:26 upstream 1f07476ec143 a5b7566c .config console log report
ci-upstream-kasan-gce 2018/01/24 03:06 upstream 1f07476ec143 a5b7566c .config console log report
ci-upstream-kasan-gce 2018/01/23 10:43 upstream a0ec1ded22e6 228e3d95 .config console log report
ci-upstream-kasan-gce 2018/01/23 10:13 upstream a0ec1ded22e6 228e3d95 .config console log report
ci-upstream-kasan-gce 2018/01/23 03:15 upstream a0ec1ded22e6 228e3d95 .config console log report
ci-upstream-kasan-gce 2018/01/16 16:17 upstream a8750ddca918 4198e588 .config console log report
ci-upstream-kasan-gce-386 2018/02/05 02:47 upstream 35277995e179 a1bc9d40 .config console log report
ci-upstream-kasan-gce-386 2018/02/05 02:27 upstream 35277995e179 a1bc9d40 .config console log report
ci-upstream-kasan-gce-386 2018/02/05 01:13 upstream 35277995e179 a1bc9d40 .config console log report
ci-upstream-kasan-gce-386 2018/02/04 21:36 upstream 617aebe6a97e a1bc9d40 .config console log report
* Struck through repros no longer work on HEAD.