INFO: task hung in __rq_qos_throttle

Status: upstream: reported C repro on 2026/08/10 12:40
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+5372ea9b426367b39933@syzkaller.appspotmail.com
First crash: 55d, last: 7d15h
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2026/09/15 upstream (ToT) 9b87fdc9af2f C [report] INFO: task hung in jbd2_journal_commit_transaction
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in __rq_qos_throttle origin:upstream 1 syz, C 11 1d21h 60d 0/3 upstream: reported C repro on 2026/08/05 16:53
upstream INFO: task hung in __rq_qos_throttle block 1 11 564d 743d 0/29 auto-obsoleted due to no activity on 2025/06/17 16:47
android-6-12 INFO: task hung in __rq_qos_throttle 1 syz, C 3 5d08h 42d 0/1 premoderation: reported C repro on 2026/08/23 14:30
linux-6.6 INFO: task hung in __rq_qos_throttle 1 syz, C 43 2d14h 61d 0/2 upstream: reported C repro on 2026/08/05 05:35
upstream INFO: task hung in __rq_qos_throttle (2) prio:high block 1 syz, C 202 8h57m 57d 0/29 upstream: reported C repro on 2026/08/08 20:07

Sample crash report:
INFO: task kworker/u4:5:4305 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:5    state:D stack:21696 pid: 4305 ppid:     2 flags:0x00004000
Workqueue: writeback wb_workfn (flush-8:0)
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
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
 rq_qos_wait+0x21d/0x330 block/blk-rq-qos.c:288
 __wbt_wait block/blk-wbt.c:522 [inline]
 wbt_wait+0x39e/0x680 block/blk-wbt.c:586
 __rq_qos_throttle+0x61/0xa0 block/blk-rq-qos.c:72
 rq_qos_throttle block/blk-rq-qos.h:203 [inline]
 blk_mq_submit_bio+0x434/0x1950 block/blk-mq.c:2233
 __submit_bio+0x73e/0x780 block/blk-core.c:917
 __submit_bio_noacct_mq block/blk-core.c:997 [inline]
 submit_bio_noacct+0x735/0x800 block/blk-core.c:1027
 submit_bio+0x2c6/0x550 block/blk-core.c:1089
 ext4_io_submit+0x14a/0x200 fs/ext4/page-io.c:381
 ext4_writepages+0xf2f/0x2d40 fs/ext4/inode.c:2851
 do_writepages+0x493/0x700 mm/page-writeback.c:2386
 __writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
 writeback_sb_inodes+0xaaa/0x1750 fs/fs-writeback.c:1940
 __writeback_inodes_wb+0x12a/0x3f0 fs/fs-writeback.c:2011
 wb_writeback+0x45e/0xbc0 fs/fs-writeback.c:2116
 wb_check_old_data_flush fs/fs-writeback.c:2216 [inline]
 wb_do_writeback fs/fs-writeback.c:2269 [inline]
 wb_workfn+0xb15/0xf20 fs/fs-writeback.c:2298
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
INFO: task syz.0.217:4535 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.217       state:D stack:27696 pid: 4535 ppid:  4320 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
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
 bit_wait_io+0xd/0xc0 kernel/sched/wait_bit.c:209
 __wait_on_bit kernel/sched/wait_bit.c:49 [inline]
 out_of_line_wait_on_bit+0x173/0x230 kernel/sched/wait_bit.c:64
 wait_on_bit_io include/linux/wait_bit.h:101 [inline]
 do_get_write_access+0x134/0xe40 fs/jbd2/transaction.c:1116
 jbd2_journal_get_write_access+0x108/0x140 fs/jbd2/transaction.c:1251
 __ext4_journal_get_write_access+0x24d/0x6e0 fs/ext4/ext4_jbd2.c:235
 ext4_reserve_inode_write+0x203/0x2e0 fs/ext4/inode.c:5866
 __ext4_mark_inode_dirty+0x136/0x6c0 fs/ext4/inode.c:6040
 ext4_dirty_inode+0xbf/0x100 fs/ext4/inode.c:6077
 __mark_inode_dirty+0x2c8/0xc90 fs/fs-writeback.c:2480
 generic_update_time+0x1cd/0x1f0 fs/inode.c:1881
 inode_update_time fs/inode.c:1894 [inline]
 file_update_time+0x3c0/0x440 fs/inode.c:2083
 ext4_page_mkwrite+0x1bc/0x1250 fs/ext4/inode.c:6195
 do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
 do_shared_fault mm/memory.c:4328 [inline]
 do_fault mm/memory.c:4396 [inline]
 handle_pte_fault mm/memory.c:4650 [inline]
 __handle_mm_fault mm/memory.c:4785 [inline]
 handle_mm_fault+0x1e47/0x4440 mm/memory.c:4883
 do_user_addr_fault+0x494/0xc90 arch/x86/mm/fault.c:1355
 handle_page_fault arch/x86/mm/fault.c:1443 [inline]
 exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1496
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606
RIP: 0033:0x7f1c86752aa3
RSP: 002b:00007ffdc5086060 EFLAGS: 00010246
RAX: 000000000003fde8 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000001b32b24000 RSI: 0000000000040000 RDI: 00007f1c86ac7708
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 00007ffdc50862f0
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3939:
 #0: ffff88814cf1a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
4 locks held by kworker/u4:5/4305:
 #0: ffff888141da0138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000304fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffff88814d5180e0 (&type->s_umount_key#32){++++}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff88814d51ac58 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2d40 fs/ext4/inode.c:2691
3 locks held by syz.0.217/4535:
 #0: ffff888076488828 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
 #0: ffff888076488828 (&mm->mmap_lock){++++}-{3:3}, at: do_user_addr_fault+0x2bb/0xc90 arch/x86/mm/fault.c:1296
 #1: ffff88814d518558 (sb_pagefaults){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1817 [inline]
 #1: ffff88814d518558 (sb_pagefaults){.+.+}-{0:0}, at: sb_start_pagefault include/linux/fs.h:1916 [inline]
 #1: ffff88814d518558 (sb_pagefaults){.+.+}-{0:0}, at: ext4_page_mkwrite+0x1a5/0x1250 fs/ext4/inode.c:6194
 #2: ffff88814d51c990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x12d5/0x1560 fs/jbd2/transaction.c:462
3 locks held by syz-executor/4542:
 #0: ffff88814d518460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
 #1: ffff8880753449b8 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline]
 #1: ffff8880753449b8 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: filename_create+0x20b/0x450 fs/namei.c:3886
 #2: ffff88814d51c990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x12d5/0x1560 fs/jbd2/transaction.c:462

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

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 07/24/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>
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:729

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/06 02:16 linux-5.15.y 0996e0926f6b 4f7b22a0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/09/05 15:27 linux-5.15.y 0996e0926f6b 4f7b22a0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/09/05 14:30 linux-5.15.y 0996e0926f6b 4f7b22a0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/22 18:20 linux-5.15.y 0eb903b5b519 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/14 06:26 linux-5.15.y aabd761612db b13552fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/09/27 18:50 linux-5.15.y 0248c33e835e a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/09/07 20:09 linux-5.15.y 0996e0926f6b 680aa3e1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/09/07 20:05 linux-5.15.y 0996e0926f6b 680aa3e1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/19 19:04 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/13 20:44 linux-5.15.y aabd761612db b13552fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/12 20:59 linux-5.15.y aabd761612db 359b2492 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __rq_qos_throttle
2026/08/10 12:39 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 __rq_qos_throttle
* Struck through repros no longer work on HEAD.