syzbot


INFO: task hung in __get_metapage

Status: upstream: reported C repro on 2023/01/08 09:57
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+aa6edd85a49b9f529d52@syzkaller.appspotmail.com
First crash: 644d, last: 644d
Fix bisection: failed (error log, bisect log)
  
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __get_metapage (2) jfs C 300 1d15h 221d 0/28 upstream: reported C repro on 2024/03/06 10:57
linux-5.15 INFO: task hung in __get_metapage (2) origin:upstream C 265 1d12h 190d 0/3 upstream: reported C repro on 2024/04/06 18:07
upstream INFO: task hung in __get_metapage jfs C error done 32 279d 733d 25/28 fixed on 2024/02/21 18:23
linux-6.1 INFO: task hung in __get_metapage (2) 9 3d10h 69d 0/3 upstream: reported on 2024/08/05 17:54
linux-6.1 INFO: task hung in __get_metapage 49 153d 185d 0/3 auto-obsoleted due to no activity on 2024/07/22 01:46
linux-5.15 INFO: task hung in __get_metapage 1 554d 554d 0/3 auto-obsoleted due to no activity on 2023/08/06 10:00

Sample crash report:
INFO: task jfsCommit:1985 blocked for more than 140 seconds.
      Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
jfsCommit       D28152  1985      2 0x80000000
Call Trace:
 context_switch kernel/sched/core.c:2828 [inline]
 __schedule+0x887/0x2040 kernel/sched/core.c:3517
 schedule+0x8d/0x1b0 kernel/sched/core.c:3561
 io_schedule+0xb5/0x120 kernel/sched/core.c:5181
 __lock_metapage fs/jfs/jfs_metapage.c:62 [inline]
 lock_metapage fs/jfs/jfs_metapage.c:76 [inline]
 __get_metapage+0xdfe/0x13d0 fs/jfs/jfs_metapage.c:653
 diIAGRead fs/jfs/jfs_imap.c:2677 [inline]
 diFree+0x6fb/0x29c0 fs/jfs/jfs_imap.c:970
 jfs_evict_inode+0x1a1/0x210 fs/jfs/inode.c:165
 evict+0x2ed/0x760 fs/inode.c:559
 iput_final fs/inode.c:1555 [inline]
 iput+0x4f1/0x860 fs/inode.c:1581
 txUpdateMap+0xd88/0x1000 fs/jfs/jfs_txnmgr.c:2412
 txLazyCommit fs/jfs/jfs_txnmgr.c:2709 [inline]
 jfs_lazycommit+0x525/0x9d0 fs/jfs/jfs_txnmgr.c:2777
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Showing all locks held in the system:
1 lock held by khungtaskd/1570:
 #0: 00000000b0be6eeb (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
2 locks held by jfsCommit/1985:
 #0: 00000000051b17c0 (&(imap->im_aglock[index])){+.+.}, at: diFree+0x24c/0x29c0 fs/jfs/jfs_imap.c:900
 #1: 000000002b1aa33a (&jfs_ip->rdwrlock/1){.+.+}, at: diFree+0x269/0x29c0 fs/jfs/jfs_imap.c:905
1 lock held by in:imklog/7764:
 #0: 00000000afb70d7a (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by syz-executor106/15511:

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

NMI backtrace for cpu 1
CPU: 1 PID: 1570 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
 watchdog+0x991/0xe60 kernel/hung_task.c:287
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4705 Comm: systemd-udevd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__lock_acquire+0x82/0x3ff0 kernel/locking/lockdep.c:3275
Code: 25 c0 df 01 00 48 89 04 24 48 8d 84 24 98 00 00 00 48 c1 e8 03 48 89 44 24 08 48 01 d0 c7 00 f1 f1 f1 f1 c7 40 04 00 f2 f2 f2 <c7> 40 08 00 00 00 f2 c7 40 0c f2 f2 f2 f2 c7 40 18 f3 f3 f3 f3 65
RSP: 0018:ffff88809864f3f0 EFLAGS: 00000082
RAX: ffffed10130c9e91 RBX: 0000000000000000 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000000 RDI: ffffffff8a070900
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000000
R13: ffff888098646200 R14: ffffffff8a070900 R15: 0000000000000001
FS:  00007efee10398c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005565c3426000 CR3: 00000000987e3000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
 __mutex_lock_common kernel/locking/mutex.c:937 [inline]
 __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078
 kernfs_dop_revalidate+0x98/0x3a0 fs/kernfs/dir.c:570
 d_revalidate fs/namei.c:767 [inline]
 lookup_fast+0xaa1/0x1080 fs/namei.c:1621
 walk_component+0xde/0xda0 fs/namei.c:1807
 link_path_walk.part.0+0x901/0x1230 fs/namei.c:2142
 link_path_walk fs/namei.c:2270 [inline]
 path_lookupat+0xe4/0x8d0 fs/namei.c:2318
 filename_lookup+0x1ac/0x5a0 fs/namei.c:2349
 user_path_at include/linux/namei.h:57 [inline]
 vfs_statx+0x113/0x210 fs/stat.c:185
 vfs_lstat include/linux/fs.h:3137 [inline]
 __do_sys_newlstat fs/stat.c:350 [inline]
 __se_sys_newlstat+0x96/0x120 fs/stat.c:344
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7efedfeab335
Code: 69 db 2b 00 64 c7 00 16 00 00 00 b8 ff ff ff ff c3 0f 1f 40 00 83 ff 01 48 89 f0 77 30 48 89 c7 48 89 d6 b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 03 f3 c3 90 48 8b 15 31 db 2b 00 f7 d8 64 89
RSP: 002b:00007ffc47114c28 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: ffffffffffffffda RBX: 00005565c3401a20 RCX: 00007efedfeab335
RDX: 00007ffc47114c60 RSI: 00007ffc47114c60 RDI: 00005565c3400a20
RBP: 00007ffc47114d20 R08: 00007efee016a1e8 R09: 0000000000001010
R10: 00007efee0169b58 R11: 0000000000000246 R12: 00005565c3400a20
R13: 00005565c3400a40 R14: 00005565c33f1e7b R15: 00005565c33f1e80

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/08 09:57 linux-4.19.y 3f8a27f9e27b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [mounted in repro] ci2-linux-4-19 INFO: task hung in __get_metapage
* Struck through repros no longer work on HEAD.