syzbot

 sign-in | mailing list | source | docs
🐞 Open [1642]
≡ Subsystems
🐞 Fixed [6108]
🐞 Invalid [15306]
⬇ Missing Backports [171]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

INFO: task hung in __x64_sys_io_destroy

Status: auto-closed as invalid on 2019/10/07 05:18
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+2eb72911e1b5139da5e2@syzkaller.appspotmail.com
First crash: 2336d, last: 2178d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
INFO: task hung in __x64_sys_io_destroy 0 (1) 2019/02/17 08:10
▶ ▼ Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in __x64_sys_io_destroy C done 1 2017d 2017d 1/1 fixed on 2019/12/07 19:18

Sample crash report:
INFO: task syz-executor.1:31675 blocked for more than 143 seconds.
      Not tainted 5.1.0-rc4+ #61
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1  D29632 31675   7567 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2877 [inline]
 __schedule+0x817/0x1cc0 kernel/sched/core.c:3518
 schedule+0x92/0x180 kernel/sched/core.c:3562
 schedule_timeout+0x8ca/0xfd0 kernel/time/timer.c:1779
 do_wait_for_common kernel/sched/completion.c:83 [inline]
 __wait_for_common kernel/sched/completion.c:104 [inline]
 wait_for_common kernel/sched/completion.c:115 [inline]
 wait_for_completion+0x29c/0x440 kernel/sched/completion.c:136
 __do_sys_io_destroy fs/aio.c:1405 [inline]
 __se_sys_io_destroy fs/aio.c:1383 [inline]
 __x64_sys_io_destroy+0x373/0x420 fs/aio.c:1383
 do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4582f9
Code: Bad RIP value.
RSP: 002b:00007fb24c6a6c78 EFLAGS: 00000246 ORIG_RAX: 00000000000000cf
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000004582f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fb24c686000
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb24c6a76d4
R13: 00000000004bf431 R14: 00000000004d1188 R15: 00000000ffffffff

Showing all locks held in the system:
1 lock held by khungtaskd/1042:
 #0: 000000003afbb9dd (rcu_read_lock){....}, at: debug_show_all_locks+0x5f/0x27e kernel/locking/lockdep.c:5061
2 locks held by udevd/3877:
1 lock held by rsyslogd/7437:
 #0: 00000000723b0925 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xee/0x110 fs/file.c:801
2 locks held by getty/7526:
 #0: 000000000af593e4 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000f71b4760 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7527:
 #0: 00000000956c9a90 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 000000004641c45f (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7528:
 #0: 000000003814f6c4 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000b7eaf4d5 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7529:
 #0: 0000000054e97373 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000c29077ef (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7530:
 #0: 00000000bff97588 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000bf9dca85 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7531:
 #0: 00000000ec1e3eaf (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 000000009b61d647 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7532:
 #0: 000000008f55012f (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 000000005bce89fd (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156

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

NMI backtrace for cpu 1
CPU: 1 PID: 1042 Comm: khungtaskd Not tainted 5.1.0-rc4+ #61
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1be/0x236 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:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
 watchdog+0x9b7/0xec0 kernel/hung_task.c:288
 kthread+0x357/0x430 kernel/kthread.c:253
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Sending NMI from CPU 1 to CPUs 0:

Crashes (50):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/04/10 05:17 upstream 869e3305f23d 65b612b7 .config console log report ci-upstream-kasan-gce
2019/04/08 22:57 upstream fd008d1a7a20 0dfb0452 .config console log report ci-upstream-kasan-gce-smack-root
2019/04/08 12:42 upstream fcf88917dd43 c34fde03 .config console log report ci-upstream-kasan-gce
2019/04/08 01:45 upstream 3b0468914708 c34fde03 .config console log report ci-upstream-kasan-gce-smack-root
2019/04/07 19:52 upstream 3b0468914708 c34fde03 .config console log report ci-upstream-kasan-gce
2019/04/07 15:55 upstream faac51ddac45 c34fde03 .config console log report ci-upstream-kasan-gce-root
2019/04/07 14:52 upstream faac51ddac45 c34fde03 .config console log report ci-upstream-kasan-gce-root
2019/04/07 09:30 upstream faac51ddac45 c34fde03 .config console log report ci-upstream-kasan-gce-selinux-root
2019/04/06 18:55 upstream f654f0fc0bd3 c34fde03 .config console log report ci-upstream-kasan-gce-smack-root
2019/04/06 05:19 upstream 7f46774c6480 fa763482 .config console log report ci-upstream-kasan-gce-root
2019/04/06 03:43 upstream 7f46774c6480 fa763482 .config console log report ci-upstream-kasan-gce
2019/04/05 00:57 upstream 145f47c7381d e5d1b3ac .config console log report ci-upstream-kasan-gce-root
2019/04/05 00:06 upstream 145f47c7381d e5d1b3ac .config console log report ci-upstream-kasan-gce
2019/04/04 14:52 upstream 145f47c7381d 6a475fff .config console log report ci-upstream-kasan-gce
2019/04/04 14:49 upstream 145f47c7381d 6a475fff .config console log report ci-upstream-kasan-gce-root
2019/04/04 06:52 upstream 8ed86627f715 d6fc4177 .config console log report ci-upstream-kasan-gce-smack-root
2019/04/04 03:13 upstream 8ed86627f715 d6fc4177 .config console log report ci-upstream-kasan-gce
2019/04/03 14:07 upstream a816fd6b49b6 dfd3394d .config console log report ci-upstream-kasan-gce-selinux-root
2019/04/03 13:03 upstream a816fd6b49b6 dfd3394d .config console log report ci-upstream-kasan-gce
2019/04/03 09:36 upstream a816fd6b49b6 dfd3394d .config console log report ci-upstream-kasan-gce-selinux-root
2019/04/02 19:29 upstream 5e7a8ca31926 dfd3394d .config console log report ci-upstream-kasan-gce-smack-root
2019/04/02 16:31 upstream 5e7a8ca31926 dfd3394d .config console log report ci-upstream-kasan-gce
2019/04/02 15:31 upstream 5e7a8ca31926 dfd3394d .config console log report ci-upstream-kasan-gce
2019/03/24 17:24 upstream 1bdd3dbfff7a acbc5b7d .config console log report ci-upstream-kasan-gce-selinux-root
2019/03/24 05:52 upstream a5ed1e96cafd a2cef203 .config console log report ci-upstream-kasan-gce
2019/03/23 06:18 upstream fd1f297b794c 3361bde5 .config console log report ci-upstream-kasan-gce
2019/03/23 02:52 upstream fd1f297b794c 3361bde5 .config console log report ci-upstream-kasan-gce-root
2019/03/15 22:08 upstream f261c4e529da bab43553 .config console log report ci-upstream-kasan-gce-selinux-root
2019/03/15 04:02 upstream 3b319ee220a8 d72db19b .config console log report ci-upstream-kasan-gce
2019/03/14 14:25 upstream fa3d493f7a57 d09a902e .config console log report ci-upstream-kasan-gce
2019/03/14 10:51 upstream fa3d493f7a57 d09a902e .config console log report ci-upstream-kasan-gce-selinux-root
2019/03/12 19:52 upstream ea295481b6e3 a71bfb62 .config console log report ci-upstream-kasan-gce
2019/03/12 19:52 upstream ea295481b6e3 a71bfb62 .config console log report ci-upstream-kasan-gce
2019/03/11 00:44 upstream 065b6c4c913d 12365b99 .config console log report ci-upstream-kasan-gce-smack-root
2019/03/10 12:55 upstream 6cdc577a18a6 12365b99 .config console log report ci-upstream-kasan-gce
2019/02/26 03:07 upstream 7d762d69145a 8022bafd .config console log report ci-upstream-kasan-gce-root
2019/02/25 07:46 upstream c3619a482e15 7a06e792 .config console log report ci-upstream-kasan-gce-root
2019/02/25 05:28 upstream c3619a482e15 7a06e792 .config console log report ci-upstream-kasan-gce-smack-root
2019/02/22 15:16 upstream 8a61716ff2ab 6a5fcca4 .config console log report ci-upstream-kasan-gce-selinux-root
2019/02/06 08:18 upstream 8834f5600cf3 d672172c .config console log report ci-upstream-kasan-gce-smack-root
2019/01/21 15:41 upstream 49a57857aeea badbbeee .config console log report ci-upstream-kasan-gce
2019/01/19 22:32 upstream 2339e91d0e66 8aa587b0 .config console log report ci-upstream-kasan-gce-root
2019/01/18 19:33 upstream d7393226d15a 2103a236 .config console log report ci-upstream-kasan-gce
2018/11/03 23:16 upstream d2ff0ff2c23f 8bd6bd63 .config console log report ci-upstream-kasan-gce-smack-root
2019/04/02 20:06 linux-next 05d08e2995cb dfd3394d .config console log report ci-upstream-linux-next-kasan-gce-root
2019/03/26 23:25 linux-next ab8bba4ec4b9 55684ce1 .config console log report ci-upstream-linux-next-kasan-gce-root
2019/03/11 09:58 linux-next cf08baa29613 12365b99 .config console log report ci-upstream-linux-next-kasan-gce-root
2019/03/10 23:06 linux-next cf08baa29613 12365b99 .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.