syzbot


INFO: task hung in __get_metapage (2)

Status: upstream: reported C repro on 2024/04/06 18:07
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+02652caa999f98dede40@syzkaller.appspotmail.com
First crash: 615d, last: 4h08m
Bug presence (1)
Date Name Commit Repro Result
2024/04/23 upstream (ToT) 71b1543c83d6 C [report] INFO: task hung in lock_metapage
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __get_metapage (2) jfs 1 C 386 now 646d 0/29 upstream: reported C repro on 2024/03/06 10:57
linux-6.1 INFO: task hung in __get_metapage (3) origin:upstream 1 C error 67 17h45m 324d 0/3 upstream: reported C repro on 2025/01/23 06:39
upstream INFO: task hung in __get_metapage jfs 1 C error done 32 705d 1158d 25/29 fixed on 2024/02/21 18:23
linux-6.1 INFO: task hung in __get_metapage (2) 1 15 414d 494d 0/3 auto-obsoleted due to no activity on 2025/01/12 16:13
linux-6.1 INFO: task hung in __get_metapage 1 49 579d 610d 0/3 auto-obsoleted due to no activity on 2024/07/22 01:46
linux-4.19 INFO: task hung in __get_metapage jfs 1 C error 1 1069d 1069d 0/1 upstream: reported C repro on 2023/01/08 09:57
linux-5.15 INFO: task hung in __get_metapage 1 1 979d 979d 0/3 auto-obsoleted due to no activity on 2023/08/06 10:00
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/12/06 11:39 17m retest repro linux-5.15.y report log
2025/12/06 11:39 19m retest repro linux-5.15.y OK log
2025/12/06 11:39 14m retest repro linux-5.15.y report log
2025/11/22 04:37 12m retest repro linux-5.15.y report log
2025/11/22 04:37 15m retest repro linux-5.15.y report log
2025/09/17 06:15 18m retest repro linux-5.15.y report log
2025/09/17 06:15 22m retest repro linux-5.15.y report log
2025/09/17 06:15 21m retest repro linux-5.15.y report log
2025/09/03 04:32 24m retest repro linux-5.15.y OK log
2025/09/03 04:32 17m retest repro linux-5.15.y OK log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2025/11/07 16:04 1h22m bisect fix linux-5.15.y OK (0) job log log
2024/06/27 21:33 1h17m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
INFO: task jfsCommit:276 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:27584 pid:  276 ppid:     2 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11bb/0x4390 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
 __lock_metapage+0x1a9/0x380 fs/jfs/jfs_metapage.c:49
 lock_metapage fs/jfs/jfs_metapage.c:63 [inline]
 __get_metapage+0x43e/0x1060 fs/jfs/jfs_metapage.c:640
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x898/0x2460 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x327/0x430 fs/jfs/inode.c:162
 evict+0x485/0x870 fs/inode.c:647
 txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
 jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
INFO: task jfsCommit:277 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26824 pid:  277 ppid:     2 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11bb/0x4390 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
 __lock_metapage+0x1a9/0x380 fs/jfs/jfs_metapage.c:49
 lock_metapage fs/jfs/jfs_metapage.c:63 [inline]
 __get_metapage+0x43e/0x1060 fs/jfs/jfs_metapage.c:640
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x898/0x2460 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x327/0x430 fs/jfs/inode.c:162
 evict+0x485/0x870 fs/inode.c:647
 txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
 jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
INFO: task syz-executor:4322 blocked for more than 146 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor    state:D stack:21984 pid: 4322 ppid:     1 flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11bb/0x4390 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 jfs_flush_journal+0x70d/0xeb0 fs/jfs/jfs_logmgr.c:1572
 jfs_sync_fs+0x79/0xa0 fs/jfs/super.c:689
 sync_filesystem+0x1be/0x220 fs/sync.c:66
 generic_shutdown_super+0x6b/0x300 fs/super.c:448
 kill_block_super+0x7c/0xe0 fs/super.c:1427
 deactivate_locked_super+0x93/0xf0 fs/super.c:335
 cleanup_mnt+0x418/0x4d0 fs/namespace.c:1148
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 exit_task_work include/linux/task_work.h:33 [inline]
 do_exit+0x61e/0x20a0 kernel/exit.c:883
 do_group_exit+0x12e/0x300 kernel/exit.c:997
 __do_sys_exit_group kernel/exit.c:1008 [inline]
 __se_sys_exit_group kernel/exit.c:1006 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1006
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2e03542749
RSP: 002b:00007ffc7a717dd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f2e035c6da2 RCX: 00007f2e03542749
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000002 R08: 00007ffc7a715b77 R09: 00007ffc7a719090
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc7a719090
R13: 00007f2e035c6d7d R14: 0000000000024576 R15: 00007ffc7a71b250
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by jfsCommit/276:
 #0: ffff888024c80920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a4/0x2460 fs/jfs/jfs_imap.c:889
 #1: ffff8880588f41f8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2c2/0x2460 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/277:
 #0: ffff88807c568920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a4/0x2460 fs/jfs/jfs_imap.c:889
 #1: ffff88805e342638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2c2/0x2460 fs/jfs/jfs_imap.c:894
2 locks held by getty/3947:
 #0: ffff88802c643098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900026562e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/4322:
 #0: ffff88807bf5c0e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
2 locks held by syz-executor/4328:
 #0: ffff8880758400e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor/4329:
 #0: ffff888079b2c0e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor/4333:
 #0: ffff88807829c0e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor/4810:
 #0: ffff88807c7860e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
1 lock held by syz-executor/5142:
 #0: ffff888079bda0e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
1 lock held by udevd/5144:
1 lock held by syz-executor/5145:
 #0: ffff8880797e40e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
2 locks held by syz-executor/5149:
 #0: ffff8880613100e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor/5181:
 #0: ffff8880204340e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffffffff8c4c3d08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb0/0x520 fs/jfs/jfs_logmgr.c:1452
1 lock held by syz-executor/6031:
 #0: ffff88801fcdc0e0 (&type->s_umount_key#54){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
2 locks held by syz.4.450/7960:
2 locks held by dhcpcd/7965:
 #0: ffff8880744f2010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff8880744f2010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:650 [inline]
 #0: ffff8880744f2010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1346
 #1: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #1: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
2 locks held by syz.5.451/7967:
2 locks held by syz.3.452/7969:
2 locks held by syz.2.453/7970:
1 lock held by syz.0.454/7978:
1 lock held by dhcpcd-run-hook/7979:

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe0f/0xe50 kernel/hung_task.c:369
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 7960 Comm: syz.4.450 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__lock_acquire+0xe42/0x7c60 kernel/locking/lockdep.c:-1
Code: 00 84 c0 0f 85 90 5d 00 00 83 3d 38 02 af 14 00 0f 95 c0 49 83 ff ff 0f 94 c1 08 c1 0f 84 1c 4f 00 00 c7 44 24 68 00 00 00 00 <48> 8b 5c 24 78 48 89 d8 48 c1 e8 03 42 80 3c 00 00 74 12 48 89 df
RSP: 0018:ffffc90003b9f2e0 EFLAGS: 00000002
RAX: 0000000000000000 RBX: ffff88802a53e420 RCX: ffffffff960b0f01
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ffaa0c0
RBP: ffffc90003b9f530 R08: dffffc0000000000 R09: fffffbfff1ff5419
R10: fffffbfff1ff5419 R11: 1ffffffff1ff5418 R12: ffff88802a53e450
R13: ffff88802a53d940 R14: 1ffff110054a7c84 R15: ffffffffffffffff
FS:  0000555582d65500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f7e9946950 CR3: 000000002a8bc000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 rcu_lock_acquire+0x20/0x30 include/linux/rcupdate.h:313
 rcu_read_lock include/linux/rcupdate.h:740 [inline]
 percpu_ref_put_many include/linux/percpu-refcount.h:317 [inline]
 percpu_ref_put+0x16/0x150 include/linux/percpu-refcount.h:338
 __mem_cgroup_uncharge_list+0x6c/0xc0 mm/memcontrol.c:7004
 mem_cgroup_uncharge_list include/linux/memcontrol.h:720 [inline]
 release_pages+0x1843/0x1bb0 mm/swap.c:962
 __pagevec_release+0x6d/0xe0 mm/swap.c:983
 pagevec_release include/linux/pagevec.h:81 [inline]
 shmem_undo_range+0x5cb/0x1880 mm/shmem.c:964
 shmem_truncate_range mm/shmem.c:1063 [inline]
 shmem_evict_inode+0x20d/0xa00 mm/shmem.c:1145
 evict+0x485/0x870 fs/inode.c:647
 __dentry_kill+0x431/0x650 fs/dcache.c:586
 dentry_kill+0xb8/0x290 fs/dcache.c:-1
 dput+0xd8/0x1a0 fs/dcache.c:893
 __fput+0x5ee/0x930 fs/file_table.c:319
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f7b293ac3aa
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 43 91 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 a3 91 02 00 8b 44 24
RSP: 002b:00007ffe04890920 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f7b293ac3aa
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000010 R08: 0000000000000000 R09: 00000000000061f7
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000003
R13: 00007ffe04890a10 R14: 0000555582d654a8 R15: 00007f7b2061d000
 </TASK>

Crashes (476):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/08 13:05 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/07/31 03:53 linux-5.15.y c79648372d02 f8f2b4da .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/03/02 21:20 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2024/04/08 02:38 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/04/24 21:09 linux-5.15.y f7347f400572 9882047a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2024/11/28 19:14 linux-5.15.y 0a51d2d4527b 5df23865 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/12/13 04:47 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/12/11 18:04 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/12/08 08:16 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/09/28 03:43 linux-5.15.y 43bb85222e53 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/09/21 06:20 linux-5.15.y 43bb85222e53 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/09/17 06:45 linux-5.15.y 43bb85222e53 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/08/17 07:34 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/07/24 18:52 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/07/21 04:21 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/04/17 03:53 linux-5.15.y f7347f400572 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/04/16 17:03 linux-5.15.y f7347f400572 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/06 16:22 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/06 05:51 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/05 17:38 linux-5.15.y c16c81c81336 4dc70884 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/05 00:16 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/04 03:49 linux-5.15.y c16c81c81336 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/03 14:43 linux-5.15.y c16c81c81336 a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/03 14:35 linux-5.15.y c16c81c81336 a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/02 00:04 linux-5.15.y c16c81c81336 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/02/01 12:52 linux-5.15.y 003148680b79 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/31 21:21 linux-5.15.y 003148680b79 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/30 20:08 linux-5.15.y 003148680b79 4c6ac32f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/30 05:55 linux-5.15.y 003148680b79 afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/29 04:09 linux-5.15.y 003148680b79 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/28 16:08 linux-5.15.y 003148680b79 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/28 04:07 linux-5.15.y 003148680b79 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/28 04:02 linux-5.15.y 003148680b79 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/27 15:09 linux-5.15.y 003148680b79 d99a33ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/25 08:22 linux-5.15.y 003148680b79 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/24 19:32 linux-5.15.y 003148680b79 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/24 17:45 linux-5.15.y 003148680b79 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/23 22:05 linux-5.15.y 003148680b79 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/22 19:00 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/22 19:00 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/21 16:24 linux-5.15.y 4735586da88e 6e87cfa2 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/21 13:04 linux-5.15.y 4735586da88e 6e87cfa2 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/20 19:26 linux-5.15.y 4735586da88e 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/18 17:43 linux-5.15.y 4735586da88e f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/18 05:01 linux-5.15.y 4735586da88e f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/17 14:54 linux-5.15.y 4735586da88e 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/01/16 17:34 linux-5.15.y 4735586da88e f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2024/04/06 18:06 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __get_metapage
2025/07/25 11:46 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/07/22 05:41 linux-5.15.y c79648372d02 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/07/16 02:00 linux-5.15.y 89950c454265 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/07/09 00:45 linux-5.15.y 3dea0e7f549e 4d9fdfa4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/05/17 15:32 linux-5.15.y 3b8db0e4f263 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/05/08 21:46 linux-5.15.y 16fdf2c7111b dbf35fa1 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/01/28 02:13 linux-5.15.y 003148680b79 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/01/23 06:31 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
2025/01/22 10:54 linux-5.15.y 4735586da88e da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
* Struck through repros no longer work on HEAD.