syzbot


INFO: task hung in lock_metapage

Status: upstream: reported C repro on 2022/10/26 22:58
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+1d84a1682e4673d5c4fb@syzkaller.appspotmail.com
First crash: 1202d, last: 50m
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: INFO: task hung in lock_metapage (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (22)
Title Replies (including bot) Last reply
[syzbot] Monthly jfs report (Jan 2026) 0 (1) 2026/01/26 07:12
[syzbot] Monthly jfs report (Dec 2025) 0 (1) 2025/12/26 07:48
[syzbot] Monthly jfs report (Nov 2025) 0 (1) 2025/11/25 08:46
[syzbot] Monthly jfs report (Oct 2025) 0 (1) 2025/10/24 18:48
[syzbot] Monthly jfs report (Sep 2025) 0 (1) 2025/09/23 06:49
[syzbot] Monthly jfs report (Aug 2025) 0 (1) 2025/08/23 16:31
[syzbot] Monthly jfs report (Jul 2025) 0 (1) 2025/07/22 12:43
[syzbot] Monthly jfs report (Jun 2025) 0 (1) 2025/06/23 07:31
[syzbot] Monthly jfs report (May 2025) 0 (1) 2025/05/21 14:56
[syzbot] Monthly jfs report (Apr 2025) 0 (1) 2025/04/22 10:11
[syzbot] Monthly jfs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly jfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly jfs report (Jan 2025) 0 (1) 2025/01/16 10:11
[syzbot] Monthly jfs report (Dec 2024) 0 (1) 2024/12/16 09:45
[syzbot] Monthly jfs report (Nov 2024) 0 (1) 2024/11/15 10:49
[syzbot] Monthly jfs report (Oct 2024) 0 (1) 2024/10/14 19:37
[syzbot] Monthly jfs report (Sep 2024) 0 (1) 2024/09/13 10:03
[syzbot] Monthly jfs report (Aug 2024) 0 (1) 2024/08/13 08:52
[syzbot] Monthly jfs report (Jul 2024) 0 (1) 2024/07/12 12:56
[syzbot] Monthly jfs report (Jun 2024) 0 (1) 2024/06/11 08:27
[syzbot] Monthly jfs report (May 2024) 0 (1) 2024/05/08 14:26
[syzbot] INFO: task hung in lock_metapage 0 (1) 2022/10/26 22:58
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 INFO: task hung in lock_metapage origin:upstream 1 C error 30 3d03h 200d 0/2 upstream: reported C repro on 2025/07/20 10:34
linux-6.1 INFO: task hung in lock_metapage origin:upstream 1 C error 270 3d03h 664d 0/3 upstream: reported C repro on 2024/04/13 05:49
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/03/04 23:44 15m retest repro upstream report log
2024/01/27 11:16 22m retest repro upstream OK log
2024/01/25 08:03 23m retest repro upstream OK log
2023/12/23 12:54 18m retest repro upstream report log
2023/11/15 04:17 2h53m retest repro upstream report log
2023/11/15 04:17 33m retest repro upstream report log
2023/11/15 00:40 40m retest repro linux-next OK log
2023/11/15 00:40 23m retest repro linux-next OK log
2023/11/15 00:40 23m retest repro linux-next OK log
2023/09/26 03:39 17m retest repro upstream report log
Fix bisection attempts (6)
Created Duration User Patch Repo Result
2024/02/01 15:58 12h04m bisect fix upstream error job log
2023/07/18 00:12 1h40m bisect fix upstream OK (0) job log log
2023/06/04 10:17 31m bisect fix upstream OK (0) job log log
2023/05/04 22:11 29m bisect fix upstream OK (0) job log log
2023/04/04 21:39 31m bisect fix upstream OK (0) job log log
2023/01/27 14:55 31m bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task jfsCommit:123 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26936 pid:123   tgid:123   ppid:2      task_flags:0x200040 flags:0x00080000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5260 [inline]
 __schedule+0x1472/0x4fe0 kernel/sched/core.c:6867
 __schedule_loop kernel/sched/core.c:6949 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:6964
 io_schedule+0x80/0xe0 kernel/sched/core.c:7791
 __lock_metapage fs/jfs/jfs_metapage.c:52 [inline]
 lock_metapage+0x1ff/0x400 fs/jfs/jfs_metapage.c:66
 __get_metapage+0x49a/0xde0 fs/jfs/jfs_metapage.c:748
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x9dd/0x2ca0 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x331/0x440 fs/jfs/inode.c:162
 evict+0x61e/0xb10 fs/inode.c:837
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>

Showing all locks held in the system:
4 locks held by pr/legacy/17:
1 lock held by khungtaskd/39:
 #0: ffffffff8dbc77c0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8dbc77c0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8dbc77c0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by jfsCommit/122:
 #0: ffff888038928900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x2e8/0x2ca0 fs/jfs/jfs_imap.c:889
 #1: ffff888052652868 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x306/0x2ca0 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/123:
 #0: ffff888032550900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x2e8/0x2ca0 fs/jfs/jfs_imap.c:889
 #1: ffff888052712868 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x306/0x2ca0 fs/jfs/jfs_imap.c:894
6 locks held by kworker/u8:13/3574:
3 locks held by kworker/u9:1/5118:
2 locks held by getty/5556:
 #0: ffff8880302ca0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003e7e2e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13c0 drivers/tty/n_tty.c:2211
3 locks held by syz-executor/6105:
2 locks held by syz-executor/6127:
2 locks held by syz-executor/6151:
 #0: ffff8880587ce0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880587ce0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880587ce0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8e03eef8 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6179:
 #0: ffff8880336400d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880336400d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880336400d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8e03eef8 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6207:
 #0: ffff888056f280d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888056f280d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888056f280d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8e03eef8 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
1 lock held by syz-executor/6236:
 #0: ffff8880587f80d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880587f80d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880587f80d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
1 lock held by syz-executor/6395:
 #0: ffff888062d5a0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888062d5a0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888062d5a0d0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
1 lock held by syz-executor/6423:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 39 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xf90/0xfe0 kernel/hung_task.c:515
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 5118 Comm: kworker/u9:1 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: hci2 hci_cmd_sync_work
RIP: 0010:__bfs kernel/locking/lockdep.c:1815 [inline]
RIP: 0010:__bfs_backwards kernel/locking/lockdep.c:1860 [inline]
RIP: 0010:check_irq_usage kernel/locking/lockdep.c:2796 [inline]
RIP: 0010:check_prev_add kernel/locking/lockdep.c:3169 [inline]
RIP: 0010:check_prevs_add kernel/locking/lockdep.c:3284 [inline]
RIP: 0010:validate_chain kernel/locking/lockdep.c:3908 [inline]
RIP: 0010:__lock_acquire+0x197b/0x2cf0 kernel/locking/lockdep.c:5237
Code: 13 25 ff 0f 00 00 39 05 4f 3b 8e 11 73 06 89 05 47 3b 8e 11 48 8b 02 48 89 df 4c 39 e8 0f 84 2c fe ff ff 4c 89 60 30 48 8b 00 <4c> 39 e8 75 f4 48 89 df e9 18 fe ff ff 48 89 fb 48 c7 c7 10 4a a9
RSP: 0018:ffffc9001004f038 EFLAGS: 00000002
RAX: ffffffff95b41b28 RBX: 00000000000003cd RCX: 0000000000000241
RDX: ffffffff95b0cb48 RSI: ffff888035398c30 RDI: 00000000000003cd
RBP: 64fbe9ef116fbce9 R08: ffffc9001004f000 R09: 0000000000000020
R10: dffffc0000000000 R11: ffffffff819f4dd0 R12: ffffffff95b340d8
R13: ffffffff92ce61d8 R14: ffff888035398000 R15: 0000000000000240
FS:  0000000000000000(0000) GS:ffff8881265c9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb3f236f000 CR3: 0000000031b40000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
 do_write_seqcount_begin_nested include/linux/seqlock.h:477 [inline]
 do_write_seqcount_begin include/linux/seqlock.h:503 [inline]
 psi_write_begin+0xab/0x160 kernel/sched/psi.c:183
 psi_task_switch+0x53/0x880 kernel/sched/psi.c:933
 psi_sched_switch kernel/sched/stats.h:225 [inline]
 __schedule+0x247b/0x4fe0 kernel/sched/core.c:6861
 __schedule_loop kernel/sched/core.c:6949 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:6964
 schedule_timeout+0x158/0x2c0 kernel/time/sleep_timeout.c:99
 __hci_cmd_sync_sk+0x632/0xd10 net/bluetooth/hci_sync.c:176
 __hci_cmd_sync_status_sk net/bluetooth/hci_sync.c:263 [inline]
 hci_disconnect_sync+0x1ec/0x3c0 net/bluetooth/hci_sync.c:5550
 hci_abort_conn_sync+0x14d/0x1190 net/bluetooth/hci_sync.c:-1
 hci_cmd_sync_work+0x213/0x400 net/bluetooth/hci_sync.c:332
 process_one_work kernel/workqueue.c:3257 [inline]
 process_scheduled_works+0xaec/0x17a0 kernel/workqueue.c:3340
 worker_thread+0xda6/0x1360 kernel/workqueue.c:3421
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>

Crashes (4669):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/31 18:49 upstream ad9a728a3388 afc0c4d4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2026/01/12 04:31 upstream 9c7ef209cd0f d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/10 04:32 upstream cb015814f8b6 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/03 09:24 upstream d61f1cc5db79 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/01 11:49 upstream 7d0a66e4bb90 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/07 14:08 upstream c746c3b51698 8ef35d49 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/08/03 10:48 upstream 186f3edfdd41 7368264b .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 lock_metapage
2025/07/20 20:05 upstream f4a40a4282f4 7117feec .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/19 03:41 upstream d786aba32000 f550e092 .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 lock_metapage
2025/01/03 12:13 upstream 0bc21e701a6f d3ccff63 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/09/06 10:23 upstream ad618736883b 464ac2ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/04/26 04:43 upstream e33c4963bf53 8bdc0f22 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/04/08 03:55 upstream fe46a7dd189e ca620dd8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/02/19 23:23 upstream b401b621758e 3af7dd65 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2023/02/12 19:57 upstream f339c2597ebb 93e26d60 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/08 07:29 upstream c2f2b01b74be d1b870e1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/11/15 15:57 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/11/15 12:19 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/11/15 08:48 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/09/22 01:54 upstream f975f08c2e89 67c37560 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/06/11 08:44 upstream aef17cb3d3c4 5d7e17ca .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2026/01/12 03:03 linux-next f417b7ffcbef d6526ea3 .config console 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 lock_metapage
2025/12/09 15:01 linux-next c75caf76ed86 d6526ea3 .config console 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 lock_metapage
2024/12/09 15:29 linux-next af2ea8ab7a54 9ac0fdc6 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2023/07/28 09:12 upstream 57012c57536f 92476829 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root INFO: task hung in lock_metapage
2022/10/22 22:51 upstream 4da34b7d175d c0b80a55 .config strace log report syz C [disk image] [vmlinux] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2023/03/05 21:39 linux-next 1acf39ef8f14 f8902b57 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2023/02/13 06:11 linux-next 38d2b86a665b 93e26d60 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2022/11/20 15:27 linux-next 15f3bff12cf6 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2026/02/06 09:06 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/06 07:19 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/06 07:19 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/06 03:24 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 23:58 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 20:55 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 18:57 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 17:31 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 15:48 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 13:28 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 11:34 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 10:24 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 10:24 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 08:26 upstream f14faaf3a1fb ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 07:12 upstream f14faaf3a1fb ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 05:38 upstream f14faaf3a1fb ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 04:13 upstream f14faaf3a1fb ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 02:53 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/05 00:22 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 22:55 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 18:36 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 16:07 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 14:41 upstream 5fd0a1df5d05 ea10c935 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 13:12 upstream 5fd0a1df5d05 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 11:29 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 10:20 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2026/02/04 05:53 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 04:43 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 03:01 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 01:45 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/04 01:20 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2026/02/03 23:48 upstream de0674d9bc69 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 19:25 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 17:07 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 15:15 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 13:41 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 12:25 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2026/02/03 11:24 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 11:23 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/03 03:23 upstream dee65f79364c d78927dd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2026/02/03 01:58 upstream dee65f79364c d78927dd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/02 23:32 upstream dee65f79364c d78927dd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/02 19:58 upstream 18f7fcd5e69a 018ebef2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2026/02/02 18:36 upstream 18f7fcd5e69a 018ebef2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2024/06/26 05:49 upstream 55027e689933 dec8bc94 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in lock_metapage
2024/06/16 23:12 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in lock_metapage
2026/01/28 14:53 linux-next 4f938c7d3b25 004c195c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
* Struck through repros no longer work on HEAD.