INFO: task hung in do_fb_ioctl

Status: upstream: reported on 2026/08/01 07:10
Reported-by: syzbot+e2b30c831377dd0afd3b@syzkaller.appspotmail.com
First crash: 95d, last: 1d02h
▶ ▼ Similar bugs (11)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in do_fb_ioctl (4) fbdev 1 1 1269d 1269d 0/29 auto-obsoleted due to no activity on 2023/07/13 16:33
upstream INFO: task hung in do_fb_ioctl (3) fbdev 1 2 1496d 1521d 0/29 auto-obsoleted due to no activity on 2023/01/02 23:29
upstream BUG: workqueue lockup (5) prio:low kernel 1 syz, C done 18124 4h40m 2485d 0/29 upstream: reported C repro on 2020/01/14 22:04
upstream INFO: task hung in do_fb_ioctl (5) fbdev 1 1 776d 776d 0/29 auto-obsoleted due to no activity on 2024/12/17 19:15
upstream INFO: task hung in do_fb_ioctl (2) fbdev 1 1 1716d 1716d 0/29 auto-closed as invalid on 2022/05/22 20:52
linux-6.1 INFO: task hung in do_fb_ioctl 1 1 465d 465d 0/3 auto-obsoleted due to no activity on 2025/11/04 03:50
linux-6.6 INFO: task hung in do_fb_ioctl 1 1 393d 393d 0/2 auto-obsoleted due to no activity on 2026/01/15 02:24
linux-4.19 INFO: task hung in do_fb_ioctl 1 1 2490d 2490d 0/1 auto-closed as invalid on 2020/05/08 18:42
upstream INFO: task hung in do_fb_ioctl fbdev 1 47 2280d 2488d 0/29 closed as dup on 2020/07/27 22:56
linux-4.14 INFO: task hung in do_fb_ioctl 1 syz, C error 24 2169d 2528d 0/1 upstream: reported C repro on 2019/12/03 05:09
linux-4.19 INFO: task hung in do_fb_ioctl (2) 1 syz, C done 7 1900d 2315d 1/1 fixed on 2021/09/21 12:35

Sample crash report:
INFO: task syz.1.441:6146 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.441       state:D stack:25824 pid: 6146 ppid:  4201 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11c3/0x4350 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
 __down_common+0x289/0x3b0 kernel/locking/semaphore.c:228
 down+0x7e/0xd0 kernel/locking/semaphore.c:63
 console_lock+0x29/0x70 kernel/printk/printk.c:2557
 do_fb_ioctl+0x642/0x850 drivers/video/fbdev/core/fbmem.c:1125
 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:0x7f24c8faab19
RSP: 002b:00007f24c7201028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f24c9230fa0 RCX: 00007f24c8faab19
RDX: 00002000000015c0 RSI: 0000000000004601 RDI: 000000000000000a
RBP: 00007f24c9042af8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f24c9231038 R14: 00007f24c9230fa0 R15: 00007ffc926cbb98
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8d11efa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/0:1H/151:
2 locks held by getty/3950:
 #0: ffff88802cb6d098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002d032e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:10/4482:
3 locks held by kworker/0:16/5102:
1 lock held by syz.4.363/5798:
2 locks held by syz.6.487/6302:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2049 [inline]
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2132
 #1: ffff8880604981c0 (&tty->legacy_mutex){+.+.}-{3:3}, at: tty_init_dev+0x6f/0x470 drivers/tty/tty_io.c:1417
1 lock held by syz.5.500/6336:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2049 [inline]
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2132
1 lock held by syz.3.541/6737:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.9.740/7585:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.4.744/7614:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.1.752/7654:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2049 [inline]
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2132
1 lock held by syz.6.871/8233:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2049 [inline]
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2132
1 lock held by syz.0.917/8448:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.964/8709:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
3 locks held by kworker/u4:15/8780:
3 locks held by kworker/u4:17/8784:
4 locks held by kworker/u4:18/8785:
2 locks held by kworker/u4:19/8787:
 #0: ffff888017879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc90003dcfd00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
1 lock held by syz.3.998/8899:
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2049 [inline]
 #0: ffffffff8d7f6ee8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2132
1 lock held by syz.9.1043/9063:
1 lock held by modprobe/9060:

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a2/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+0xe1b/0xe60 kernel/hung_task.c:369
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/03 07:10 linux-5.15.y 700e62ea909a 6969b601 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in do_fb_ioctl
2026/08/30 04:08 linux-5.15.y 28c35638ec51 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in do_fb_ioctl
2026/08/15 20:16 linux-5.15.y aabd761612db 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in do_fb_ioctl
2026/08/09 19:36 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in do_fb_ioctl
2026/08/01 07:10 linux-5.15.y 6e2fd6534337 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in do_fb_ioctl
* Struck through repros no longer work on HEAD.