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: 768d, last: 11d
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 Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in nbd_ioctl 1 C done 18 2045d 2119d 1/1 fixed on 2019/12/28 10:32
linux-4.14 INFO: task hung in nbd_ioctl (2) 1 C done 16 1792d 2038d 1/1 fixed on 2020/10/21 11:01
upstream INFO: task hung in nbd_ioctl (2) nbd 1 37 1800d 1853d 15/29 fixed on 2020/09/25 01:17
upstream INFO: task hung in nbd_ioctl nbd 1 C done 71 2097d 2132d 13/29 fixed on 2019/11/06 12:39
linux-6.1 INFO: task hung in nbd_ioctl origin:upstream 1 C error 7 202d 831d 0/3 upstream: reported C repro on 2023/04/23 23:29
linux-4.19 INFO: task hung in nbd_ioctl 1 C error 79 907d 2121d 0/1 upstream: reported C repro on 2019/10/12 13:11
upstream INFO: task hung in nbd_ioctl (3) nbd 1 C done unreliable 143 10d 1769d 0/29 upstream: reported C repro on 2020/09/28 07:17
linux-4.14 INFO: task hung in nbd_ioctl (3) 1 C inconclusive 12 1172d 1723d 0/1 upstream: reported C repro on 2020/11/13 07:37
upstream INFO: task can't die in nbd_ioctl nbd 1 C done 7 41d 1762d 0/29 upstream: reported C repro on 2020/10/05 07:20
Last patch testing requests (9)
Created Duration User Patch Repo Result
2025/07/22 10:47 16m retest repro linux-5.15.y report log
2025/07/22 10:47 13m retest repro linux-5.15.y report log
2025/07/22 10:47 17m retest repro linux-5.15.y report log
2025/07/22 10:47 17m retest repro linux-5.15.y report log
2025/07/22 10:47 13m retest repro linux-5.15.y report log
2025/05/31 08:16 16m retest repro linux-5.15.y report log
2025/05/07 02:36 13m retest repro linux-5.15.y report log
2025/05/07 02:36 13m retest repro linux-5.15.y report log
2025/05/07 02:36 13m retest repro linux-5.15.y report log

Sample crash report:
INFO: task syz.0.16:4367 blocked for more than 143 seconds.
      Not tainted 5.15.186-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.16        state:D stack:26240 pid: 4367 ppid:  4304 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1e0 kernel/sched/core.c:6459
 schedule_timeout+0x97/0x280 kernel/time/timer.c:1890
 do_wait_for_common+0x29a/0x440 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+0x63a/0x1380 kernel/workqueue.c:2882
 nbd_start_device_ioctl drivers/block/nbd.c:1365 [inline]
 __nbd_ioctl drivers/block/nbd.c:1427 [inline]
 nbd_ioctl+0xaea/0xe40 drivers/block/nbd.c:1467
 blkdev_ioctl+0x33c/0x690 block/ioctl.c:604
 block_ioctl+0xac/0xf0 block/fops.c:496
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f50d8350929
RSP: 002b:00007ffc7b7e46a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f50d8577fa0 RCX: 00007f50d8350929
RDX: 0000000000000000 RSI: 000000000000ab03 RDI: 0000000000000003
RBP: 00007f50d83d2b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f50d8577fa0 R14: 00007f50d8577fa0 R15: 0000000000000002
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c11bfa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u5:0/146:
 #0: ffff888147949138 ((wq_completion)nbd3-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000170fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by getty/3948:
 #0: ffff88802b72f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
2 locks held by kworker/u5:1/4240:
 #0: ffff8880202cb138 ((wq_completion)nbd0-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90002f6fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/u5:2/4242:
 #0: ffff8880203b0138 ((wq_completion)nbd4-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90002f9fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/1:8/4268:
 #0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90002fefd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
3 locks held by kworker/1:9/4269:
 #0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90002fffd00 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffffffff8d236ec8 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
3 locks held by kworker/1:12/4272:
 #0: ffff88802a824138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000308fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffffffff8d236ec8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4116
3 locks held by kworker/0:12/4329:
 #0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000323fd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffff88805a302240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x271/0x3240 drivers/net/netdevsim/fib.c:1480
2 locks held by kworker/u5:3/4379:
 #0: ffff888020332938 ((wq_completion)nbd1-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000337fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/u5:4/4403:
 #0: ffff888020399938 ((wq_completion)nbd2-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000347fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/u5:5/4425:
 #0: ffff88802095d138 ((wq_completion)nbd6-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000357fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
4 locks held by kworker/u4:5/4439:
 #0: ffff888016879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000361fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffffffff8d236ec8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
 #3: ffffffff8c120a28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #3: ffffffff8c120a28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
2 locks held by kworker/u5:7/4481:
 #0: ffff8880203b6938 ((wq_completion)nbd5-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000378fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/u5:8/4509:
 #0: ffff888020979938 ((wq_completion)nbd8-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000384fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by kworker/u5:9/4537:
 #0: ffff8880209b6138 ((wq_completion)nbd7-recv){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000395fd00 ((work_completion)(&args->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
1 lock held by syz-executor/4600:
 #0: ffffffff8d236ec8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d236ec8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x974/0xe60 net/core/rtnetlink.c:5647

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe0f/0xe50 kernel/hung_task.c:369
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </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 default_idle+0xb/0x10 arch/x86/kernel/process.c:728

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/06 08:15 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
2025/07/06 06:52 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nbd_ioctl
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.