syzbot


INFO: task hung in lock_metapage

Status: upstream: reported C repro on 2024/04/13 05:49
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+a9dcfad4f4f16393f167@syzkaller.appspotmail.com
First crash: 753d, last: 9d03h
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2024/04/26 upstream (ToT) c942a0cd3603 C [report] VFS: Busy inodes after unmount (use-after-free)
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 59 8d22h 290d 0/2 upstream: reported C repro on 2025/07/20 10:34
upstream INFO: task hung in lock_metapage jfs 1 C inconclusive error 4956 19d 1287d 0/29 upstream: reported C repro on 2022/10/26 22:58
Fix bisection attempts (9)
Created Duration User Patch Repo Result
2025/11/20 04:51 0m bisect fix linux-6.1.y error job log
2025/10/20 06:34 2h12m bisect fix linux-6.1.y OK (0) job log log
2025/09/15 01:52 1h38m bisect fix linux-6.1.y OK (0) job log log
2025/07/02 09:32 2h15m bisect fix linux-6.1.y OK (0) job log log
2025/06/01 21:09 2h37m bisect fix linux-6.1.y OK (0) job log log
2025/04/28 15:49 2h52m bisect fix linux-6.1.y OK (0) job log log
2025/03/06 08:21 1h46m bisect fix linux-6.1.y OK (0) job log log
2024/07/30 07:12 1h31m bisect fix linux-6.1.y OK (0) job log log
2024/06/12 18:12 1h54m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
INFO: task jfsCommit:106 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:26760 pid:106   ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5245 [inline]
 __schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
 schedule+0xb9/0x180 kernel/sched/core.c:6638
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8798
 __lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
 lock_metapage+0x1f5/0x320 fs/jfs/jfs_metapage.c:64
 __get_metapage+0x4c6/0xfa0 fs/jfs/jfs_metapage.c:639
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x8e1/0x2430 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x327/0x430 fs/jfs/inode.c:162
 evict+0x4c9/0x8d0 fs/inode.c:705
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x425/0xa70 fs/jfs/jfs_txnmgr.c:2733
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cb2df70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cb2e790 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
 #0: ffffffff8cb2d5e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #0: ffffffff8cb2d5e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #0: ffffffff8cb2d5e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by jfsCommit/106:
 #0: ffff888079478920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2d6/0x2430 fs/jfs/jfs_imap.c:889
 #1: ffff888068b3a638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2f4/0x2430 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/107:
 #0: ffff888077ce8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2d6/0x2430 fs/jfs/jfs_imap.c:889
 #1: ffff888068b3e6f8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2f4/0x2430 fs/jfs/jfs_imap.c:894
2 locks held by getty/4023:
 #0: ffff88802fe3c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x429/0x1390 drivers/tty/n_tty.c:2198
2 locks held by syz-executor/4439:
 #0: ffff888078a440e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
 #1: ffffffff8cf2ae08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/4454:
 #0: ffff88805b6ee0e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
 #1: ffffffff8cf2ae08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/4469:
 #0: ffff88802c9440e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
 #1: ffffffff8cf2ae08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/4484:
 #0: ffff88807c1740e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
 #1: ffffffff8cf2ae08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/4510:
 #0: ffff8880542320e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
 #1: ffffffff8cf2ae08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1444
1 lock held by syz-executor/4531:
 #0: ffff888075f8a0e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
1 lock held by syz-executor/4685:
 #0: ffff888057a460e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
1 lock held by syz-executor/4834:
 #0: ffff88801fe900e0 (&type->s_umount_key#53){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362

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

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 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xeee/0xf30 kernel/hung_task.c:377
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 41 Comm: kworker/u4:2 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: bat_events batadv_nc_worker
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:35 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_local_irq_save arch/x86/include/asm/irqflags.h:106 [inline]
RIP: 0010:lock_acquire+0x166/0x4a0 kernel/locking/lockdep.c:5658
Code: 0f 85 2f 02 00 00 41 83 3e 00 0f 85 18 01 00 00 43 c6 44 3d 08 00 48 c7 84 24 a0 00 00 00 00 00 00 00 9c 8f 84 24 a0 00 00 00 <4c> 8b b4 24 a0 00 00 00 43 c6 44 3d 08 f8 fa 48 c7 c7 00 1e 8c 8a
RSP: 0018:ffffc90000b27ac0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: c11d56fd1b61c700
RDX: 0000000000000000 RSI: ffffffff8adf1380 RDI: ffffffff8adf1340
RBP: ffffc90000b27bc8 R08: ffffffff8e1ff42f R09: 1ffffffff1c3fe85
R10: dffffc0000000000 R11: fffffbfff1c3fe86 R12: 0000000000000001
R13: 1ffff92000164f64 R14: ffff88801b2aa89c R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559fd54a2168 CR3: 000000007e73d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 rcu_read_lock include/linux/rcupdate.h:791 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
 batadv_nc_worker+0xeb/0x600 net/batman-adv/network-coding.c:719
 process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
 worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>

Crashes (316):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/25 17:53 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/02 23:47 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2024/12/28 07:40 linux-6.1.y 563edd786f0a d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2024/04/26 01:04 linux-6.1.y 6741e066ec76 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/19 14:49 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/19 09:25 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/19 03:58 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/18 22:36 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/18 17:06 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/18 04:21 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/17 03:07 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/16 21:21 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/27 14:29 linux-6.1.y 7c87defbd336 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/27 08:12 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/27 05:44 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/26 20:55 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/26 09:03 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/26 06:58 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/26 06:47 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/25 11:02 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/25 10:58 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/04/18 02:00 linux-6.1.y 8e8fc038cad5 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/02/17 00:43 linux-6.1.y 8ce36b2849ef 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/02/03 06:49 linux-6.1.y cd9b81672742 d78927dd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2026/01/31 07:54 linux-6.1.y cd9b81672742 c75a2f6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/27 17:18 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/17 20:40 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/12 20:50 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/04 22:10 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/12/02 19:18 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/09/15 07:05 linux-6.1.y 3db754f56897 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/08/07 09:57 linux-6.1.y 3594f306da12 9a42d6b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/07/20 04:53 linux-6.1.y 3369c6df2fae 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/03/25 19:51 linux-6.1.y 344a09659766 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/03/18 05:32 linux-6.1.y 344a09659766 ce3352cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/02/04 03:44 linux-6.1.y 0cbb5f65e52f 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/02/03 17:16 linux-6.1.y 0cbb5f65e52f a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/02/03 17:14 linux-6.1.y 0cbb5f65e52f a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/02/01 23:47 linux-6.1.y 0cbb5f65e52f 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/31 19:35 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/30 18:35 linux-6.1.y 75cefdf153f5 4c6ac32f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/30 05:48 linux-6.1.y 75cefdf153f5 afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/29 18:14 linux-6.1.y 75cefdf153f5 136953f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/29 03:51 linux-6.1.y 75cefdf153f5 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/28 15:38 linux-6.1.y 75cefdf153f5 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/28 15:38 linux-6.1.y 75cefdf153f5 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/28 04:26 linux-6.1.y 75cefdf153f5 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/27 14:13 linux-6.1.y 75cefdf153f5 d99a33ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/25 07:54 linux-6.1.y 75cefdf153f5 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/24 17:43 linux-6.1.y 75cefdf153f5 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/24 05:58 linux-6.1.y 75cefdf153f5 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/24 05:57 linux-6.1.y 75cefdf153f5 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/23 21:45 linux-6.1.y 75cefdf153f5 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/23 10:44 linux-6.1.y f4f677285b38 a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/22 22:30 linux-6.1.y f4f677285b38 a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/22 18:27 linux-6.1.y f4f677285b38 a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/22 05:07 linux-6.1.y f4f677285b38 da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2025/01/08 02:18 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2024/12/28 01:44 linux-6.1.y 563edd786f0a d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
2024/04/13 05:48 linux-6.1.y bf1e3b1cb1e0 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_metapage
* Struck through repros no longer work on HEAD.