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: 1094d, last: 1d21h
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 (18)
Title Replies (including bot) Last reply
[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 13 32d 92d 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 251 17h17m 555d 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:112 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:26920 pid:112   tgid:112   ppid:2      task_flags:0x200040 flags:0x00080000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5325 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6929
 __schedule_loop kernel/sched/core.c:7011 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7026
 io_schedule+0x80/0xd0 kernel/sched/core.c:7871
 __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:162
 evict+0x504/0x9c0 fs/inode.c:810
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x43f/0xa90 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:158
 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: ffffffff8dd3d220 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8dd3d220 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8dd3d220 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by jfsCommit/111:
 #0: ffff888076b38920 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x29f/0x2c40 fs/jfs/jfs_imap.c:889
 #1: ffff888054aaef18 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x2bd/0x2c40 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/112:
 #0: ffff88807d738920 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x29f/0x2c40 fs/jfs/jfs_imap.c:889
 #1: ffff888054aaa5d8 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x2bd/0x2c40 fs/jfs/jfs_imap.c:894
2 locks held by getty/5594:
 #0: ffff8880332cd0a0 (&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
2 locks held by syz-executor/5976:
 #0: ffff88807c4f60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88807c4f60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88807c4f60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/5980:
 #0: ffff888057fca0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888057fca0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888057fca0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/5982:
 #0: ffff888054da60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888054da60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888054da60e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/5988:
 #0: ffff88807a5820e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88807a5820e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88807a5820e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/5989:
 #0: ffff888076ae20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888076ae20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888076ae20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6318:
 #0: ffff88807cdb20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88807cdb20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88807cdb20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
1 lock held by syz-executor/6345:
 #0: ffff88807dbea0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88807dbea0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88807dbea0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
2 locks held by syz-executor/6382:
 #0: ffff888057ad20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888057ad20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888057ad20e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6412:
 #0: ffff888032ff40e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888032ff40e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888032ff40e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
 #1: ffffffff8e17d748 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
1 lock held by syz-executor/6438:
 #0: ffff88805ba3c0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88805ba3c0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88805ba3c0e0 (&type->s_umount_key#55){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505
1 lock held by syz.1.388/7937:
2 locks held by syz.3.389/7944:
6 locks held by syz.4.391/7946:
2 locks held by syz.5.390/7947:
2 locks held by syz.6.392/7950:
2 locks held by syz.2.393/7954:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/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+0x439/0x7d0 arch/x86/kernel/process.c:158
 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: 7954 Comm: syz.2.393 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0033:0x7fb631450cab
Code: cd 48 01 c1 49 39 4f 08 72 4c 8d 4d ff 85 ed 74 33 66 0f 1f 44 00 00 48 39 f0 72 1b 4d 8b 07 49 89 c1 49 29 f1 47 0f b6 0c 08 <45> 84 c9 74 08 45 88 0c 00 49 8b 47 10 48 83 c0 01 49 89 47 10 83
RSP: 002b:00007ffd8ebca8d0 EFLAGS: 00000216
RAX: 0000000000eca200 RBX: 00007ffd8ebca970 RCX: 0000000000000025
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007ffd8ebcaa10
RBP: 0000000000000102 R08: 00007fb628600000 R09: 0000000000000000
R10: 0000000000000000 R11: 00007ffd8ebca980 R12: 0000000000000001
R13: 00007fb63162db80 R14: 0000000000000000 R15: 00007ffd8ebcaa10
FS:  000055557cfbe500 GS:  0000000000000000

Crashes (3711):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/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
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/10/19 04:07 upstream 1c64efcb083c 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/18 13:46 upstream f406055cb18c 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/15 11:44 upstream 9b332cece987 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/14 10:28 upstream 3a8660878839 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/10/14 08:52 upstream 3a8660878839 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/14 01:21 upstream 3a8660878839 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/14 00:00 upstream 3a8660878839 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/13 02:41 upstream 3a8660878839 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/11 17:55 upstream 0739473694c4 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/04 19:37 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/03 13:23 upstream e406d57be7bd 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/02 10:34 upstream 080ffb4bec4d 267f56c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/28 07:42 upstream 51a24b7deaae 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/09/24 00:07 upstream cec1e6e5d1ab e667a34f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/23 12:30 upstream cec1e6e5d1ab 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/23 11:28 upstream cec1e6e5d1ab 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/21 23:25 upstream 2d5bd41a4505 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/20 11:30 upstream cd89d487374c 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/17 15:38 upstream 5aca7966d2a7 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/09/15 13:02 upstream f83ec76bf285 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/09/15 06:44 upstream f83ec76bf285 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/09/14 21:07 upstream f83a4f2a4d8c e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/13 05:50 upstream 22f20375f5b7 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/12 18:03 upstream 320475fbd590 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/12 10:53 upstream 320475fbd590 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/10 11:59 upstream 9dd1835ecda5 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/09/09 06:09 upstream f777d1112ee5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/07 11:16 upstream b236920731dd d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/06 01:48 upstream c8ed9b5c02a5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/04 22:38 upstream 08b06c30a445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/03 10:26 upstream e6b9dce0aeeb 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/02 23:45 upstream e6b9dce0aeeb 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/09/01 12:23 upstream b320789d6883 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/31 00:39 upstream 11e7861d680c 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/08/30 23:08 upstream 11e7861d680c 807a3b61 .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/10/17 10:26 linux-next 2433b8476165 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/10/05 15:30 linux-next 47a8d4b89844 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/10/02 06:08 linux-next 3b9b1f8df454 a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/14 17:04 linux-next 590b221ed425 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/11 09:23 linux-next 5f540c4aade9 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/08 04:28 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/07 14:13 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/07 05:24 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/09/06 23:57 linux-next be5d4872e528 d291dd2d .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.