INFO: task jfsCommit:97 blocked for more than 143 seconds. Not tainted 6.9.0-rc4-syzkaller-g6a71d2909427 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:jfsCommit state:D stack:0 pid:97 tgid:97 ppid:2 flags:0x00000008 Call trace: __switch_to+0x314/0x560 arch/arm64/kernel/process.c:553 context_switch kernel/sched/core.c:5409 [inline] __schedule+0x14bc/0x24ec kernel/sched/core.c:6746 __schedule_loop kernel/sched/core.c:6823 [inline] schedule+0xbc/0x238 kernel/sched/core.c:6838 io_schedule+0x8c/0x12c kernel/sched/core.c:9044 __lock_metapage+0x1cc/0x458 fs/jfs/jfs_metapage.c:50 lock_metapage fs/jfs/jfs_metapage.c:64 [inline] __get_metapage+0x970/0x1054 fs/jfs/jfs_metapage.c:639 diIAGRead+0xe4/0x14c fs/jfs/jfs_imap.c:2669 diFree+0x800/0x2648 fs/jfs/jfs_imap.c:956 jfs_evict_inode+0x2d0/0x3f4 fs/jfs/inode.c:156 evict+0x260/0x68c fs/inode.c:667 iput_final fs/inode.c:1741 [inline] iput+0x760/0x844 fs/inode.c:1767 txUpdateMap+0x73c/0x8e4 fs/jfs/jfs_txnmgr.c:2367 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x3bc/0x9a8 fs/jfs/jfs_txnmgr.c:2733 kthread+0x288/0x310 kernel/kthread.c:388 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 Showing all locks held in the system: 1 lock held by khungtaskd/30: #0: ffff80008f0578c0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:328 2 locks held by kworker/u8:2/41: #0: ffff0000c0031148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x668/0x15d4 kernel/workqueue.c:3228 #1: ffff800095277c20 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work+0x6b4/0x15d4 kernel/workqueue.c:3228 2 locks held by jfsCommit/97: #0: ffff0000d87c8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:886 #1: ffff0000dfecb8b8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:891 2 locks held by getty/5996: #0: ffff0000cc2f90a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340 #1: ffff800097bab2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41c/0x1228 drivers/tty/n_tty.c:2201 3 locks held by kworker/0:4/6305: #0: ffff0000c0028948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x668/0x15d4 kernel/workqueue.c:3228 #1: ffff800097bd7c20 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x6b4/0x15d4 kernel/workqueue.c:3228 #2: ffff0000fccc6240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x270/0x32bc drivers/net/netdevsim/fib.c:1489 4 locks held by syz-executor.4/9728: #0: ffff0000ebe1cac8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x218/0x2a4 fs/file.c:1191 #1: ffff0000e4efe420 (sb_writers#22){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2855 [inline] #1: ffff0000e4efe420 (sb_writers#22){.+.+}-{0:0}, at: vfs_write+0x368/0xc3c fs/read_write.c:586 #2: ffff0000dfecbd00 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:795 [inline] #2: ffff0000dfecbd00 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: generic_file_write_iter+0x88/0x2b4 mm/filemap.c:4092 #3: ffff0000dfecb8b8 (&jfs_ip->rdwrlock#3){++++}-{3:3}, at: jfs_get_block+0x1a4/0xb98 fs/jfs/inode.c:213 1 lock held by syz-executor.3/9770: 3 locks held by udevadm/9800: =============================================