syzbot


INFO: task hung in nbd_ioctl

Status: upstream: reported C repro on 2023/06/26 06:58
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+df34fe61d8d75eab5996@syzkaller.appspotmail.com
First crash: 471d, last: 2d13h
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2024/10/08 upstream (ToT) 87d6aab2389e C [report] INFO: task hung in nbd_ioctl
Similar bugs (9)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in nbd_ioctl C done 18 1749d 1823d 1/1 fixed on 2019/12/28 10:32
linux-4.14 INFO: task hung in nbd_ioctl (2) C done 16 1496d 1741d 1/1 fixed on 2020/10/21 11:01
upstream INFO: task hung in nbd_ioctl (2) nbd 37 1503d 1556d 15/28 fixed on 2020/09/25 01:17
upstream INFO: task hung in nbd_ioctl nbd C done 71 1800d 1836d 13/28 fixed on 2019/11/06 12:39
linux-6.1 INFO: task hung in nbd_ioctl origin:upstream C 7 20d 535d 0/3 upstream: reported C repro on 2023/04/23 23:29
linux-4.19 INFO: task hung in nbd_ioctl C error 79 610d 1824d 0/1 upstream: reported C repro on 2019/10/12 13:11
upstream INFO: task hung in nbd_ioctl (3) nbd C done unreliable 126 10d 1472d 0/28 upstream: reported C repro on 2020/09/28 07:17
linux-4.14 INFO: task hung in nbd_ioctl (3) C inconclusive 12 875d 1426d 0/1 upstream: reported C repro on 2020/11/13 07:37
upstream INFO: task can't die in nbd_ioctl nbd C done 7 26d 1465d 0/28 upstream: reported C repro on 2020/10/05 07:20
Last patch testing requests (4)
Created Duration User Patch Repo Result
2024/10/07 15:30 16m retest repro linux-5.15.y report log
2024/10/07 15:30 13m retest repro linux-5.15.y report log
2024/10/07 15:30 13m retest repro linux-5.15.y report log
2024/10/07 15:30 11m retest repro linux-5.15.y report log

Sample crash report:
INFO: task syz-executor154:3510 blocked for more than 143 seconds.
      Not tainted 5.15.127-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor154 state:D stack:26176 pid: 3510 ppid:  3509 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
 do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
 flush_workqueue+0x737/0x1610 kernel/workqueue.c:2882
 nbd_start_device_ioctl drivers/block/nbd.c:1365 [inline]
 __nbd_ioctl drivers/block/nbd.c:1427 [inline]
 nbd_ioctl+0xab8/0xe10 drivers/block/nbd.c:1467
 blkdev_ioctl+0x333/0x6b0 block/ioctl.c:601
 block_ioctl+0xb1/0xf0 block/fops.c:493
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1ad5bee879
RSP: 002b:00007ffe74809278 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1ad5bee879
RDX: 0000000000000000 RSI: 000000000000ab03 RDI: 0000000000000003
RBP: 00007f1ad5c615f0 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000006 R11: 0000000000000246 R12: 0000000000000001
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91f0a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u5:0/146:
 #0: ffff88801b5a2938 ((wq_completion)nbd0-recv){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc900010bfd20 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
2 locks held by getty/3248:
 #0: ffff88802450e098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900020162e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.127-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:109 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/08/19 16:34 linux-5.15.y f6f7927ac664 d216d8a0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2024/04/26 03:27 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
2024/04/26 01:56 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
2023/06/26 06:58 linux-5.15.y f67653019430 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
2024/04/06 08:19 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2024/04/06 08:13 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2024/03/17 04:27 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2024/01/31 23:32 linux-5.15.y 6139f2a02fe0 373b66cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2024/03/29 00:22 linux-5.15.y 9465fef4ae35 e91187ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
2024/03/17 04:05 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
2024/02/06 13:03 linux-5.15.y 6139f2a02fe0 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nbd_ioctl
* Struck through repros no longer work on HEAD.