syzbot

 sign-in | mailing list | source | docs | 🏰
🐞 Open [1346]
≡ Subsystems
🐞 Fixed [7083]
🐞 Invalid [18650]
⬇ Missing Backports [221]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
✨ AI
💬 Send us feedback

INFO: task hung in block_invalidate_folio (2)

Status: upstream: reported C repro on 2025/08/11 03:13
Subsystems: gfs2
[Documentation on labels]
Reported-by: syzbot+85194ada5aabdfff265b@syzkaller.appspotmail.com
First crash: 295d, last: 19d
Cause bisection: failed (error log, bisect log)
  
▶ ▼ Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly gfs2 report (Apr 2026) 0 (1) 2026/04/22 09:08
[syzbot] Monthly gfs2 report (Mar 2026) 0 (1) 2026/03/23 08:58
[syzbot] Monthly gfs2 report (Dec 2025) 0 (1) 2025/12/18 10:06
[syzbot] [gfs2?] INFO: task hung in block_invalidate_folio (2) 0 (1) 2025/08/11 03:13
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in block_invalidate_folio (2) 1 4 34d 80d 0/3 upstream: reported on 2026/02/14 00:20
upstream INFO: task hung in block_invalidate_folio gfs2 1 2 484d 496d 0/29 auto-obsoleted due to no activity on 2025/03/07 11:30
linux-6.6 INFO: task hung in block_invalidate_folio 1 2 36d 49d 0/2 upstream: reported on 2026/03/16 23:48
linux-6.1 INFO: task hung in block_invalidate_folio 1 syz error 1 354d 354d 0/3 auto-obsoleted due to no activity on 2025/08/24 15:41
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/05/01 13:46 1h01m retest repro upstream OK log
2026/05/01 03:53 39m retest repro linux-next report log
2026/05/01 03:43 29m retest repro linux-next report log
2026/02/13 14:15 1h01m retest repro upstream report log
2026/02/13 12:45 41m retest repro linux-next report log
2026/02/13 12:45 31m retest repro linux-next OK log
2025/11/22 14:39 31m retest repro linux-next report log
2025/09/13 12:58 29m retest repro linux-next report log
2025/09/13 12:58 22m retest repro linux-next OK log
2025/08/30 11:04 19m retest repro upstream report log
▶ ▼ Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/09/30 17:07 3h03m bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task kworker/0:2H:5960 blocked for more than 143 seconds.
      Not tainted 6.17.0-rc1-next-20250814-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:2H    state:D stack:25832 pid:5960  tgid:5960  ppid:2      task_flags:0x4208060 flags:0x00004000
Workqueue: gfs2-glock/syz:syz glock_work_func
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5357 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961
 __schedule_loop kernel/sched/core.c:7043 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7058
 io_schedule+0x80/0xd0 kernel/sched/core.c:7903
 bit_wait_io+0x11/0xd0 kernel/sched/wait_bit.c:250
 __wait_on_bit_lock+0xec/0x4f0 kernel/sched/wait_bit.c:93
 out_of_line_wait_on_bit_lock+0x123/0x170 kernel/sched/wait_bit.c:120
 wait_on_bit_lock_io include/linux/wait_bit.h:221 [inline]
 __lock_buffer fs/buffer.c:71 [inline]
 lock_buffer include/linux/buffer_head.h:432 [inline]
 discard_buffer fs/buffer.c:1606 [inline]
 block_invalidate_folio+0x376/0x730 fs/buffer.c:1663
 folio_invalidate mm/truncate.c:140 [inline]
 truncate_cleanup_folio+0x2d8/0x430 mm/truncate.c:160
 truncate_inode_pages_range+0x233/0xda0 mm/truncate.c:379
 inode_go_inval+0xf9/0x2c0 fs/gfs2/glops.c:368
 do_xmote+0x4e9/0x1060 fs/gfs2/glock.c:732
 glock_work_func+0x2a8/0x580 fs/gfs2/glock.c:1080
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
INFO: task syz-executor878:6013 blocked for more than 144 seconds.
      Not tainted 6.17.0-rc1-next-20250814-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor878 state:D stack:25224 pid:6013  tgid:6011  ppid:5871   task_flags:0x400140 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5357 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961
 __schedule_loop kernel/sched/core.c:7043 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7058
 io_schedule+0x80/0xd0 kernel/sched/core.c:7903
 bit_wait_io+0x11/0xd0 kernel/sched/wait_bit.c:250
 __wait_on_bit_lock+0xec/0x4f0 kernel/sched/wait_bit.c:93
 out_of_line_wait_on_bit_lock+0x123/0x170 kernel/sched/wait_bit.c:120
 lock_buffer include/linux/buffer_head.h:432 [inline]
 gfs2_meta_read+0x25a/0x980 fs/gfs2/meta_io.c:274
 gfs2_meta_buffer+0x10f/0x2e0 fs/gfs2/meta_io.c:498
 gfs2_meta_inode_buffer fs/gfs2/meta_io.h:70 [inline]
 punch_hole+0x802/0x2ca0 fs/gfs2/bmap.c:1796
 gfs2_iomap_end+0x4f8/0x6c0 fs/gfs2/bmap.c:1178
 iomap_iter+0x313/0xde0 fs/iomap/iter.c:79
 iomap_file_buffered_write+0x7fa/0x9b0 fs/iomap/buffered-io.c:1065
 gfs2_file_buffered_write+0x4ed/0x880 fs/gfs2/file.c:1061
 gfs2_file_write_iter+0x94e/0x1100 fs/gfs2/file.c:1166
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x5c9/0xb30 fs/read_write.c:686
 ksys_write+0x145/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb47156a4f9
RSP: 002b:00007fb471516168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fb47160a6c8 RCX: 00007fb47156a4f9
RDX: 000000000208e24b RSI: 0000200000000040 RDI: 0000000000000005
RBP: 00007fb47160a6c0 R08: 00007fb4715166c0 R09: 0000000000000000
R10: 00007fb4715166c0 R11: 0000000000000246 R12: 00007fb47160a6cc
R13: 0000000000000006 R14: 00007ffe95b7cf90 R15: 00007ffe95b7d078
 </TASK>
INFO: lockdep is turned off.
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.17.0-rc1-next-20250814-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:332 [inline]
 watchdog+0xf60/0xfa0 kernel/hung_task.c:495
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 5868 Comm: syz-executor878 Not tainted 6.17.0-rc1-next-20250814-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__do_sys_clock_nanosleep kernel/time/posix-timers.c:1399 [inline]
RIP: 0010:__se_sys_clock_nanosleep+0x2f1/0x380 kernel/time/posix-timers.c:1376
Code: df 41 80 3c 07 00 49 89 c7 74 08 4c 89 ef e8 66 3a 73 00 4d 8b 5d 00 44 89 f7 48 8b 74 24 08 48 8d 54 24 40 41 ff d3 0f 1f 00 <48> 98 eb 1d e8 56 bc 0f 00 eb 05 e8 4f bc 0f 00 48 c7 c0 ea ff ff
RSP: 0018:ffffc90003d87e20 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff888032e95fb8 RCX: 4287d3a08c5ae100
RDX: 0000000000000000 RSI: ffffffff8be34be0 RDI: ffffffff84d25ae3
RBP: ffffc90003d87ee0 R08: ffffffff8fa3b137 R09: 1ffffffff1f47626
R10: dffffc0000000000 R11: fffffbfff1f47627 R12: 0000000000000000
R13: ffffffff8b8d2870 R14: 0000000000000000 R15: dffffc0000000000
FS:  000055558d547480(0000) GS:ffff888125d0f000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb469b83000 CR3: 0000000033114000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb4715976f3
Code: 00 00 00 00 0f 1f 00 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d ae 19 07 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007ffe95b7d118 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 000000000003ece8 RCX: 00007fb4715976f3
RDX: 00007ffe95b7d130 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000001cdf R08: 00000000046c6b1b R09: 7fffffffffffffff
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffe95b7d200
R13: 0000000000000050 R14: 431bde82d7b634db R15: 00007ffe95b7d184
 </TASK>

Crashes (155):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/16 08:14 linux-next 931e46dcbc7e 1804e95e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/15 22:31 upstream 1f5ffc672165 c441f497 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/10 14:24 upstream 9a9c8ce300cd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/09 16:26 upstream 7f87a5ea75f0 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/08 05:54 upstream 3036cd0d3328 2c961e87 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/04 18:03 upstream 7ca6d1cfec80 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/04/03 04:15 upstream 5619b098e2fb 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/29 20:18 upstream f242ac4a0944 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/29 04:21 upstream be762d8b6dd7 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/20 17:40 upstream 0e4f8f1a3d08 2f245add .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/17 12:52 upstream 2d1373e4246d c01bca74 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/13 12:55 upstream 0257f64bdac7 2f7f359d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/12 11:52 upstream 80234b5ab240 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/11 00:50 upstream b4f0dd314b39 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/09 23:41 upstream 1f318b96cc84 176bead5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/07 10:40 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/07 03:07 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/04 23:44 upstream ecc64d2dc9ff a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/02 22:23 upstream af4e9ef3d784 b9dd6534 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/26 03:35 upstream d9d32e5bd5a4 e0f78d93 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/24 09:07 upstream 7dff99b35460 41d2fa6a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/16 08:21 upstream 0f2acd3148e0 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/14 21:55 upstream 770aaedb461a 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/30 12:45 upstream 4d310797262f bfa73b7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/29 16:24 upstream 8dfce8991b95 aeb6fdd5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/28 05:54 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/22 15:36 upstream a66191c590b3 2367ed1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/15 22:08 upstream 944aacb68baf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/13 14:53 upstream b71e635feefc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/12 17:31 upstream 0f61b1860cc3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2025/08/07 03:03 upstream 479058002c32 4bd24a3e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/04 12:50 linux-next c025f6cf4209 e6b6b96b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/03/03 02:55 linux-next d517cb8cea01 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/22 09:01 linux-next d4906ae14a5f 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/20 19:50 linux-next d4906ae14a5f 741f5161 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/19 19:03 linux-next 44982d352c33 73a252ac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/19 04:48 linux-next 50f68cc7be0a 746545b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/16 04:12 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/15 19:34 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/15 15:20 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/15 12:14 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/15 11:56 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/15 11:56 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/02/14 06:54 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/26 02:39 linux-next ca3a02fda4da 55756628 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/26 00:34 linux-next ca3a02fda4da 55756628 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/25 07:19 linux-next ca3a02fda4da 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/22 07:24 linux-next e3b32dcb9f23 101dad69 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2026/01/11 16:24 linux-next f417b7ffcbef d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2025/12/20 15:58 linux-next cc3aa43b44bd d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2] [mounted in repro #3] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
2025/08/16 00:33 linux-next 931e46dcbc7e 1804e95e .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in block_invalidate_folio
* Struck through repros no longer work on HEAD.