syzbot


INFO: task hung in lock_metapage

Status: upstream: reported C repro on 2025/07/20 10:34
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+4e40ac4f0b1f7535cc05@syzkaller.appspotmail.com
First crash: 39d, last: 2d19h
Bug presence (1)
Date Name Commit Repro Result
2025/07/20 upstream (ToT) 89be9a83ccf1 C [report] INFO: task hung in lock_metapage
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in lock_metapage jfs 1 C inconclusive error 3658 22h06m 1036d 0/29 upstream: reported C repro on 2022/10/26 22:58
linux-6.1 INFO: task hung in lock_metapage origin:upstream 1 C 250 21d 502d 0/3 upstream: reported C repro on 2024/04/13 05:49
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/08/25 13:02 2h50m bisect fix linux-6.6.y OK (0) job log log

Sample crash report:
INFO: task jfsCommit:113 blocked for more than 143 seconds.
      Not tainted 6.6.99-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:27656 pid:113   ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x14e2/0x4580 kernel/sched/core.c:6700
 schedule+0xbd/0x170 kernel/sched/core.c:6774
 io_schedule+0x80/0xd0 kernel/sched/core.c:9023
 __lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
 lock_metapage+0x1ec/0x310 fs/jfs/jfs_metapage.c:64
 __get_metapage+0x4ca/0xfa0 fs/jfs/jfs_metapage.c:639
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x978/0x2c10 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x32b/0x440 fs/jfs/inode.c:156
 evict+0x486/0x870 fs/inode.c:705
 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
 jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>
INFO: task jfsCommit:114 blocked for more than 144 seconds.
      Not tainted 6.6.99-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26864 pid:114   ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x14e2/0x4580 kernel/sched/core.c:6700
 schedule+0xbd/0x170 kernel/sched/core.c:6774
 io_schedule+0x80/0xd0 kernel/sched/core.c:9023
 __lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
 lock_metapage+0x1ec/0x310 fs/jfs/jfs_metapage.c:64
 __get_metapage+0x4ca/0xfa0 fs/jfs/jfs_metapage.c:639
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x978/0x2c10 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x32b/0x440 fs/jfs/inode.c:156
 evict+0x486/0x870 fs/inode.c:705
 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
 jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/1:0/23:
1 lock held by khungtaskd/28:
 #0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by jfsCommit/113:
 #0: ffff888023e98920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
 #1: ffff888076deaf78 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/114:
 #0: ffff88805d920920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
 #1: ffff88805c782638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
3 locks held by kworker/u4:9/2984:
2 locks held by getty/5548:
 #0: ffff88814c3430a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
2 locks held by syz-executor/5919:
 #0: ffff88807b9da0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88807b9da0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88807b9da0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/5923:
 #0: ffff88803155c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88803155c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88803155c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/5926:
 #0: ffff88807c35e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88807c35e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88807c35e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6212:
 #0: ffff88805ca9a0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88805ca9a0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88805ca9a0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6245:
 #0: ffff88807b09c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88807b09c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88807b09c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6351:
 #0: ffff88805f1460e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88805f1460e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88805f1460e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6407:
 #0: ffff888060a320e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff888060a320e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff888060a320e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6568:
 #0: ffff888025dea0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff888025dea0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff888025dea0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6606:
 #0: ffff88805f5ee0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88805f5ee0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88805f5ee0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
 #1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
1 lock held by syz-executor/6792:
 #0: ffff88802521c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff88802521c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff88802521c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by udevd/7363:
2 locks held by syz.4.245/7823:
2 locks held by syz.1.246/7827:
2 locks held by rm/7834:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf41/0xf80 kernel/hung_task.c:379
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 7823 Comm: syz.4.245 Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:zap_pte_range mm/memory.c:-1 [inline]
RIP: 0010:zap_pmd_range mm/memory.c:1570 [inline]
RIP: 0010:zap_pud_range mm/memory.c:1599 [inline]
RIP: 0010:zap_p4d_range mm/memory.c:1620 [inline]
RIP: 0010:unmap_page_range+0xacd/0x2fe0 mm/memory.c:1641
Code: 01 00 00 4c 89 7c 24 30 0f 84 d6 00 00 00 48 8b 7c 24 68 4c 89 fe 4c 89 f2 e8 1f ae ff ff 49 89 c6 48 83 bc 24 90 00 00 00 00 <48> 89 44 24 28 0f 84 e9 01 00 00 48 8b 54 24 58 48 89 d0 48 c1 e8
RSP: 0018:ffffc9000cc8f620 EFLAGS: 00000282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8880235f9e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000cc8f810 R08: ffffffff8e4a7cef R09: 1ffffffff1c94f9d
R10: dffffc0000000000 R11: fffffbfff1c94f9e R12: 00007f1791c00000
R13: dffffc0000000000 R14: 0000000000000000 R15: 00007f1791b76000
FS:  0000555573686500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f95d82cc000 CR3: 000000001d7b8000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 unmap_vmas+0x25e/0x3a0 mm/memory.c:1731
 unmap_region+0x1fb/0x340 mm/mmap.c:2340
 do_vmi_align_munmap+0xffe/0x1660 mm/mmap.c:2588
 do_vmi_munmap+0x252/0x2d0 mm/mmap.c:2656
 __vm_munmap+0x193/0x3c0 mm/mmap.c:2957
 __do_sys_munmap mm/mmap.c:2974 [inline]
 __se_sys_munmap mm/mmap.c:2971 [inline]
 __x64_sys_munmap+0x60/0x70 mm/mmap.c:2971
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f179a58ea37
Code: 00 00 00 48 c7 c2 a8 ff ff 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 b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe6694e798 EFLAGS: 00000246 ORIG_RAX: 000000000000000b
RAX: ffffffffffffffda RBX: 0000000001000000 RCX: 00007f179a58ea37
RDX: 0000000000000000 RSI: 0000000008400000 RDI: 00007f17911ff000
RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000623a
R10: 0000200000023d02 R11: 0000000000000246 R12: 0000000000000003
R13: 00007ffe6694e870 R14: 00007ffe6694e830 R15: 00007f17911ff000
 </TASK>

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/21 07:51 linux-6.6.y d96eb99e2f0e 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/21 03:15 linux-6.6.y d96eb99e2f0e 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/20 22:42 linux-6.6.y d96eb99e2f0e 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/20 17:47 linux-6.6.y d96eb99e2f0e 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/22 19:11 linux-6.6.y d96eb99e2f0e 8e9d1dc1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/22 04:19 linux-6.6.y d96eb99e2f0e 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/22 04:19 linux-6.6.y d96eb99e2f0e 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/22 04:19 linux-6.6.y d96eb99e2f0e 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/21 17:13 linux-6.6.y d96eb99e2f0e 56d87229 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/20 10:39 linux-6.6.y d96eb99e2f0e 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/20 10:33 linux-6.6.y d96eb99e2f0e 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
2025/07/20 10:33 linux-6.6.y d96eb99e2f0e 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in lock_metapage
* Struck through repros no longer work on HEAD.