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: 1037d, last: 1d01h
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 (17)
Title Replies (including bot) Last reply
[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 12 4h02m 36d 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 250 18d 499d 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:110 blocked for more than 143 seconds.
      Not tainted 6.16.0-syzkaller-11241-g186f3edfdd41 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26920 pid:110   tgid:110   ppid:2      task_flags:0x200040 flags:0x00004000
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
 __lock_metapage fs/jfs/jfs_metapage.c:52 [inline]
 lock_metapage+0x1f3/0x400 fs/jfs/jfs_metapage.c:66
 __get_metapage+0x497/0xde0 fs/jfs/jfs_metapage.c:748
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x983/0x2c40 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x331/0x440 fs/jfs/inode.c:156
 evict+0x504/0x9c0 fs/inode.c:810
 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
 jfs_lazycommit+0x43f/0xa90 fs/jfs/jfs_txnmgr.c:2733
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e139e60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e139e60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e139e60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by jfsCommit/110:
 #0: ffff888028d50920 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x29f/0x2c40 fs/jfs/jfs_imap.c:889
 #1: ffff888077152618 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x2bd/0x2c40 fs/jfs/jfs_imap.c:894
2 locks held by getty/5610:
 #0: ffff8880345ec0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900036bb2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by syz-executor422/6549:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-syzkaller-11241-g186f3edfdd41 #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:307 [inline]
 watchdog+0xf93/0xfe0 kernel/hung_task.c:470
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 6549 Comm: syz-executor422 Not tainted 6.16.0-syzkaller-11241-g186f3edfdd41 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x0/0x90 kernel/kcov.c:313
Code: 7c 11 10 48 89 74 11 18 48 89 44 11 20 e9 f3 9d 50 ff cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 48 8b 04 24 65 48 8b 14 25 08 60 9f 92 65 8b 0d e8 bc
RSP: 0018:ffffc900047bf4c8 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffc900047bf5f8 RCX: cbd7cb67ba707800
RDX: ffff88807bcf9e00 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffea0001ba5340 R08: ffff88807bcf9e00 R09: 0000000000000002
R10: 0000000000000003 R11: 0000000000000000 R12: ffffc900047bf5e0
R13: ffff88802f6d2af0 R14: 0000000000000000 R15: 1ffff920008f7ebf
FS:  000055557269a380(0000) GS:ffff888125c2a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe6181ff000 CR3: 000000006ee2d000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 xa_entry include/linux/xarray.h:1226 [inline]
 xas_find+0x45d/0x990 lib/xarray.c:1423
 find_get_entry mm/filemap.c:2037 [inline]
 find_lock_entries+0x1ff/0xa60 mm/filemap.c:2141
 shmem_undo_range+0x254/0x14b0 mm/shmem.c:1114
 shmem_truncate_range mm/shmem.c:1244 [inline]
 shmem_evict_inode+0x272/0xa70 mm/shmem.c:1372
 evict+0x504/0x9c0 fs/inode.c:810
 __dentry_kill+0x209/0x660 fs/dcache.c:669
 dput+0x19f/0x2b0 fs/dcache.c:911
 __fput+0x68e/0xa70 fs/file_table.c:476
 fput_close_sync+0x119/0x200 fs/file_table.c:573
 __do_sys_close fs/open.c:1587 [inline]
 __se_sys_close fs/open.c:1572 [inline]
 __x64_sys_close+0x7f/0x110 fs/open.c:1572
 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:0x7fe61f65b030
Code: ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 80 3d 51 00 08 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c
RSP: 002b:00007ffefe88d708 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 00007ffefe88d720 RCX: 00007fe61f65b030
RDX: 0000000000000010 RSI: 00007ffefe88d720 RDI: 0000000000000003
RBP: 0000000000068b52 R08: 00007fe617200000 R09: 00000000000061f9
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffefe88d8c0
R13: 00007ffefe88d760 R14: 0000000000000003 R15: 00007fe61f6a503b
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.746 msecs

Crashes (3653):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/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
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
2025/08/24 18:34 upstream c330cb607721 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/22 14:46 upstream 3957a5720157 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/08/21 06:39 upstream 41cd3fd15263 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/20 07:54 upstream b19a97d57c15 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/19 09:11 upstream be48bcf004f9 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/18 20:10 upstream c17b750b3ad9 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/18 08:20 upstream 8d561baae505 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/18 03:43 upstream 8d561baae505 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/17 23:35 upstream 8d561baae505 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/17 23:29 upstream 8d561baae505 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/17 06:51 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/17 02:27 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/17 01:04 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/16 17:40 upstream dfd4b508c8c6 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/16 05:31 upstream ee94b00c1a64 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/15 23:20 upstream ee94b00c1a64 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/14 21:07 upstream 0cc53520e68b 5d8c2ac2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/13 07:17 upstream 0e39a731820a 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/10 07:20 upstream 561c80369df0 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/08 00:19 upstream 6e64f4580381 04cffc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/08 00:19 upstream 6e64f4580381 04cffc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/07 05:51 upstream cca7a0aae895 9a42d6b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/05 19:36 upstream 7e161a991ea7 37880f40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/05 02:07 upstream d632ab86aff2 f5bcc8dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/31 16:50 upstream 260f6f4fda93 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/31 13:29 upstream 260f6f4fda93 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/31 11:54 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/31 06:44 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/30 23:56 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/30 18:11 upstream 4b290aae788e f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/30 10:38 upstream 4b290aae788e f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/30 06:02 upstream 0919a5b3b11c f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/30 04:47 upstream 0919a5b3b11c f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 23:07 upstream 0919a5b3b11c f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 21:14 upstream 0919a5b3b11c f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 18:34 upstream ae388edd4a8f c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 12:22 upstream ae388edd4a8f c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 07:56 upstream ae388edd4a8f c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 05:11 upstream ae388edd4a8f 6654ea9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/29 05:08 upstream ae388edd4a8f 6654ea9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/28 22:24 upstream 038d61fd6422 6654ea9c .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
2025/08/20 11:34 linux-next 5303936d609e 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/08/15 00:26 linux-next 931e46dcbc7e dcc075fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/08/11 20:02 linux-next b1549501188c 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/08/10 15:21 linux-next b1549501188c 32a0e5ed .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.