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

Hello,

syzbot found the following issue on:

HEAD commit: f4f677285b38 Linux 6.1.126
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f97618580000
kernel config: https://syzkaller.appspot.com/x/.config?x=175d65561bbe8acf
dashboard link: https://syzkaller.appspot.com/bug?extid=a38cceca1ef98728809f
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/29acafb07afa/disk-f4f67728.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5cf6e6722b24/vmlinux-f4f67728.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4b92c1bb1642/Image-f4f67728.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

INFO: task jfsCommit:93 blocked for more than 143 seconds.
Not tainted 6.1.126-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit state:D stack:0 pid:93 ppid:2 flags:0x00000008
Call trace:
__switch_to+0x308/0x598 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+0x418/0x894 fs/inode.c:705
iput_final fs/inode.c:1834 [inline]
iput+0x7c0/0x8a4 fs/inode.c:1860
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:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015c65530 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffff800015c65d30 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffff800015c65360 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by jfsCommit/93:
#0: ffff0000db0d8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
#1: ffff0000f3ad1cf8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
4 locks held by kworker/u4:4/186:
#0: ffff0000c03dd138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff8000210b7c20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff8000180b8cd0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf4/0xa18 net/core/net_namespace.c:583
#3: ffff0000daee13e8 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_destruct+0x11c/0x2dc drivers/net/wireguard/device.c:249
2 locks held by kworker/u4:5/1757:
1 lock held by udevd/3914:
2 locks held by getty/4056:
#0: ffff0000d63fa098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001d8102f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2198
2 locks held by syz.0.827/8111:
#0: ffff0000fe554410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#0: ffff0000fe554410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
#0: ffff0000fe554410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1400
#1: ffff0000d530c130 (sk_lock-AF_CAN){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1756 [inline]
#1: ffff0000d530c130 (sk_lock-AF_CAN){+.+.}-{0:0}, at: bcm_release+0x1bc/0x7f4 net/can/bcm.c:1533
2 locks held by syz.5.832/8126:

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



---
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 [email protected].

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

syzbot has found a reproducer for the following issue on:
console output: https://syzkaller.appspot.com/x/log.txt?x=1490f618580000
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e865df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13081c24580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/346c9840d025/mount_0.gz
INFO: task jfsCommit:92 blocked for more than 143 seconds.
task:jfsCommit state:D stack:0 pid:92 ppid:2 flags:0x00000008
2 locks held by jfsCommit/92:
#0: ffff0000d16c8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
#1: ffff0000def20138 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
#0: ffff0000de388920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
#1: ffff0000e17ca638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
2 locks held by getty/4059:
#0: ffff0000d67ca098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001d8502f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2198

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



---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.