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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 52f863f820fd Linux 6.1.120
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17cc7730580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fcb3bdeefdffc5
dashboard link: https://syzkaller.appspot.com/bug?extid=ec7cb5db60b4d8e2071b
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/0b5925d752d3/disk-52f863f8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3ce049167860/vmlinux-52f863f8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e8baa2576794/Image-52f863f8.gz.xz

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

INFO: task syz.4.866:6782 blocked for more than 143 seconds.
Tainted: G W 6.1.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.866 state:D stack:0 pid:6782 ppid:4295 flags:0x00000001
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
bit_wait_io+0x1c/0xac kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xcc/0x1e8 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x194/0x21c kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer+0x78/0xac fs/buffer.c:69
lock_buffer include/linux/buffer_head.h:397 [inline]
ext4_quota_write+0x36c/0x54c fs/ext4/super.c:7179
qtree_write_dquot+0x1e0/0x4d8 fs/quota/quota_tree.c:462
v2_write_dquot+0xf4/0x188 fs/quota/quota_v2.c:361
dquot_commit+0x14c/0x240 fs/quota/dquot.c:514
ext4_write_dquot+0x1b4/0x314 fs/ext4/super.c:6770
ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6830
mark_dquot_dirty fs/quota/dquot.c:372 [inline]
mark_all_dquot_dirty+0x108/0x424 fs/quota/dquot.c:412
__dquot_free_space+0x840/0xce4 fs/quota/dquot.c:1942
dquot_free_space_nodirty include/linux/quotaops.h:379 [inline]
ext4_xattr_inode_free_quota+0x11c/0x188 fs/ext4/xattr.c:899
ext4_xattr_set_entry+0xb2c/0x1694 fs/ext4/xattr.c:1677
ext4_xattr_block_set+0x634/0x2d10 fs/ext4/xattr.c:1910
ext4_xattr_set_handle+0xae8/0x1294 fs/ext4/xattr.c:2404
ext4_xattr_set+0x220/0x340 fs/ext4/xattr.c:2506
ext4_xattr_trusted_set+0x4c/0x64 fs/ext4/xattr_trusted.c:38
__vfs_setxattr+0x388/0x3a4 fs/xattr.c:182
__vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277
vfs_setxattr+0x1a8/0x344 fs/xattr.c:309
do_setxattr fs/xattr.c:594 [inline]
setxattr+0x230/0x294 fs/xattr.c:617
path_setxattr+0x17c/0x258 fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015c55570 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xd10 kernel/rcu/tasks.h:543
1 lock held by rcu_tasks_trace/13:
#0: ffff800015c55d90 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xd10 kernel/rcu/tasks.h:543
1 lock held by khungtaskd/28:
#0: ffff800015c553a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by getty/4056:
#0: ffff0000d653f098 (&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
1 lock held by syz-executor/4296:
#0: ffff0000f53ea0e0 (&type->s_umount_key#87){+.+.}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
1 lock held by syz-executor/4301:
#0: ffff0000d9cce0e0 (&type->s_umount_key#30){++++}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
3 locks held by syz-executor/4303:
3 locks held by kworker/0:4/4343:
#0: ffff0000c45b6938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800021907c20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000d1247190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff0000d1247190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b0/0x42e4 drivers/usb/core/hub.c:5801
4 locks held by kworker/u4:10/4565:
2 locks held by kworker/u4:14/4782:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800021e27c20 ((quota_release_work).work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
6 locks held by syz.4.866/6782:
#0: ffff0000d294a460 (sb_writers#3){++++}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000f4d09810 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff0000f4d09810 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:308
#2: ffff0000f4d094d8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff0000f4d094d8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x1e0/0x1294 fs/ext4/xattr.c:2319
#3: ffff800015d88bc8 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:349
#4: ffff0000f4ccc5e8 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x54/0x240 fs/quota/dquot.c:507
#5: ffff0000d294a208 (&s->s_dquot.dqio_sem){++++}-{3:3}, at: v2_write_dquot+0x84/0x188 fs/quota/quota_v2.c:359
1 lock held by syz.3.906/6882:
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: do_umount_root fs/namespace.c:1609 [inline]
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: do_umount fs/namespace.c:1693 [inline]
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: path_umount+0x6e0/0xd64 fs/namespace.c:1802
1 lock held by syz.3.906/6886:
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: do_umount_root fs/namespace.c:1609 [inline]
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: do_umount fs/namespace.c:1693 [inline]
#0: ffff0001085580e0 (&type->s_umount_key#30){++++}-{3:3}, at: path_umount+0x6e0/0xd64 fs/namespace.c:1802
1 lock held by syz.5.1023/7183:
#0: ffff0000f5d260e0 (&type->s_umount_key#30){++++}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
1 lock held by syz-executor/7213:
#0: ffff0000dc76e0e0 (&type->s_umount_key#30){++++}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
1 lock held by syz-executor/7388:
#0: ffff0000d45420e0 (&type->s_umount_key#30){++++}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362
1 lock held by syz.8.1168/7603:
#0: ffff0000d84360e0 (&type->s_umount_key#30){++++}-{3:3}, at: iterate_supers+0xb0/0x1dc fs/super.c:755
1 lock held by syz.3.1520/8955:
1 lock held by dhcpcd/8977:
#0: ffff0000faa98130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1750 [inline]
#0: ffff0000faa98130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x4c/0xb58 net/packet/af_packet.c:3263

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



---
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