[v6.1] INFO: task hung in __get_metapage (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 48d525b0e463 Linux 6.1.103
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111632f9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1a8b264edc2488f
dashboard link: https://syzkaller.appspot.com/bug?extid=85d03f851b3b657ad232
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/06cea92ea31f/disk-48d525b0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/83efa486ea4e/vmlinux-48d525b0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d7f6fd55583d/Image-48d525b0.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+85d03f...@syzkaller.appspotmail.com

INFO: task jfsCommit:91 blocked for more than 143 seconds.
Not tainted 6.1.103-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit state:D stack:0 pid:91 ppid:2 flags:0x00000008
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xef4/0x1d44 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
io_schedule+0x8c/0x188 kernel/sched/core.c:8786
__lock_metapage+0x1cc/0x458 fs/jfs/jfs_metapage.c:50
lock_metapage fs/jfs/jfs_metapage.c:64 [inline]
__get_metapage+0x96c/0x1050 fs/jfs/jfs_metapage.c:639
diIAGRead+0xe4/0x14c fs/jfs/jfs_imap.c:2672
diFree+0x800/0x2648 fs/jfs/jfs_imap.c:959
jfs_evict_inode+0x2d0/0x3f4 fs/jfs/inode.c:156
evict+0x260/0x68c fs/inode.c:666
iput_final fs/inode.c:1791 [inline]
iput+0x7c0/0x8a4 fs/inode.c:1817
txUpdateMap+0x73c/0x8e4 fs/jfs/jfs_txnmgr.c:2367
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x3a0/0x988 fs/jfs/jfs_txnmgr.c:2732
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864

Showing all locks held in the system:
5 locks held by kworker/u4:0/9:
#0: ffff0000c0845138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800019fe7c20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff800017fd7a10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf4/0x994 net/core/net_namespace.c:566
#3: ffff800015b9a300 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x58/0x5c4 kernel/rcu/tree.c:4018
#4: ffff0001b4357158 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
#4: ffff0001b4357158 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1355 [inline]
#4: ffff0001b4357158 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1645 [inline]
#4: ffff0001b4357158 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2c4/0x1d44 kernel/sched/core.c:6474
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015b95030 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015b95830 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015b94e60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by jfsCommit/90:
#0: ffff0000dab20920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
#1: ffff0000e28e8a78 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/91:
#0: ffff0000d00f0920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
#1: ffff0000f1d7ddb8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
4 locks held by kworker/u4:3/182:
2 locks held by getty/4056:
#0: ffff0000d6556098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001beb02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2198
3 locks held by kworker/u4:10/4567:
1 lock held by syz-executor/6674:
#0: ffff0000f67f40e0 (&type->s_umount_key#53){++++}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
1 lock held by syz.1.910/7008:
#0: ffff0000f67f40e0 (&type->s_umount_key#53){++++}-{3:3}, at: iterate_supers+0xb0/0x1dc fs/super.c:755
1 lock held by syz.3.1223/8046:

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup