======================================================
WARNING: possible circular locking dependency detected
5.15.168-syzkaller #0 Not tainted
------------------------------------------------------
syz.3.4/3655 is trying to acquire lock:
ffff88807d030ae0 (&sdp->sd_quota_mutex){+.+.}-{3:3}, at: do_qc+0xc8/0x720 fs/gfs2/quota.c:678

but task is already holding lock:
ffff888062bcd080 (&ip->i_rw_mutex){++++}-{3:3}, at: __gfs2_iomap_alloc+0x2b7/0x2090 fs/gfs2/bmap.c:681

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ip->i_rw_mutex){++++}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       down_read+0x45/0x2e0 kernel/locking/rwsem.c:1498
       __gfs2_iomap_get+0x178/0x1480 fs/gfs2/bmap.c:858
       gfs2_iomap_get fs/gfs2/bmap.c:1398 [inline]
       gfs2_block_map+0x292/0x830 fs/gfs2/bmap.c:1213
       bh_get+0x26d/0x6a0 fs/gfs2/quota.c:385
       qdsb_get+0x209/0x3b0 fs/gfs2/quota.c:518
       gfs2_quota_hold+0x19d/0x5c0 fs/gfs2/quota.c:604
       gfs2_quota_lock+0x9f/0x450 fs/gfs2/quota.c:1076
       gfs2_quota_lock_check fs/gfs2/quota.h:50 [inline]
       gfs2_iomap_begin_write fs/gfs2/bmap.c:1015 [inline]
       gfs2_iomap_begin+0x722/0x1350 fs/gfs2/bmap.c:1114
       iomap_iter+0x631/0xe30 fs/iomap/iter.c:74
       iomap_file_buffered_write+0x248/0x8a0 fs/iomap/buffered-io.c:814
       gfs2_file_buffered_write+0x3e3/0x850 fs/gfs2/file.c:1057
       gfs2_file_write_iter+0x4a2/0xf10 fs/gfs2/file.c:1165
       call_write_iter include/linux/fs.h:2174 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0xacd/0xe50 fs/read_write.c:594
       ksys_write+0x1a2/0x2c0 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&sdp->sd_quota_mutex){+.+.}-{3:3}
:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       do_qc+0xc8/0x720 fs/gfs2/quota.c:678
       gfs2_quota_change+0x2db/0x8c0 fs/gfs2/quota.c:1295
       gfs2_alloc_blocks+0x1f0a/0x2970 fs/gfs2/rgrp.c:2504
       __gfs2_iomap_alloc+0x4f0/0x2090 fs/gfs2/bmap.c:707
       gfs2_iomap_begin_write fs/gfs2/bmap.c:1049 [inline]
       gfs2_iomap_begin+0xb12/0x1350 fs/gfs2/bmap.c:1114
       iomap_iter+0x631/0xe30 fs/iomap/iter.c:74
       iomap_file_buffered_write+0x248/0x8a0 fs/iomap/buffered-io.c:814
       gfs2_file_buffered_write+0x3e3/0x850 fs/gfs2/file.c:1057
       gfs2_file_write_iter+0x4a2/0xf10 fs/gfs2/file.c:1165
       call_write_iter include/linux/fs.h:2174 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0xacd/0xe50 fs/read_write.c:594
       ksys_write+0x1a2/0x2c0 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ip->i_rw_mutex);
                               lock(&sdp->sd_quota_mutex);
                               lock(&ip->i_rw_mutex);
  lock(&sdp->sd_quota_mutex);

 *** DEADLOCK ***

6 locks held by syz.3.4/3655:
 #0: ffff88801f0b40f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2cb/0x380 fs/file.c:1057
 #1: ffff88807cbd8460 (sb_writers#14){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590
 #2: ffff888062bccbe8 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #2: ffff888062bccbe8 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: gfs2_file_write_iter+0x373/0xf10 fs/gfs2/file.c:1122
 #3: ffff88807cbd8650 (sb_internal#2){.+.+}-{0:0}, at: gfs2_trans_begin+0x6d/0xe0 fs/gfs2/trans.c:118
 #4: ffff88807d0310a8 (&sdp->sd_log_flush_lock){.+.+}-{3:3}, at: __gfs2_trans_begin+0x55a/0x940 fs/gfs2/trans.c:87
 #5: ffff888062bcd080 (&ip->i_rw_mutex){++++}-{3:3}, at: __gfs2_iomap_alloc+0x2b7/0x2090 fs/gfs2/bmap.c:681

stack backtrace:
CPU: 1 PID: 3655 Comm: syz.3.4 Not tainted 5.15.168-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 do_qc+0xc8/0x720 fs/gfs2/quota.c:678
 gfs2_quota_change+0x2db/0x8c0 fs/gfs2/quota.c:1295
 gfs2_alloc_blocks+0x1f0a/0x2970 fs/gfs2/rgrp.c:2504
 __gfs2_iomap_alloc+0x4f0/0x2090 fs/gfs2/bmap.c:707
 gfs2_iomap_begin_write fs/gfs2/bmap.c:1049 [inline]
 gfs2_iomap_begin+0xb12/0x1350 fs/gfs2/bmap.c:1114
 iomap_iter+0x631/0xe30 fs/iomap/iter.c:74
 iomap_file_buffered_write+0x248/0x8a0 fs/iomap/buffered-io.c:814
 gfs2_file_buffered_write+0x3e3/0x850 fs/gfs2/file.c:1057
 gfs2_file_write_iter+0x4a2/0xf10 fs/gfs2/file.c:1165
 call_write_iter include/linux/fs.h:2174 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0xacd/0xe50 fs/read_write.c:594
 ksys_write+0x1a2/0x2c0 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ee851fff9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8ee6998038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8ee86d7f80 RCX: 00007f8ee851fff9
RDX: 0000000000000012 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007f8ee8592296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f8ee86d7f80 R15: 00007ffc51fe14d8
 </TASK>
==================================================================
BUG: KASAN: stack-out-of-bounds in should_fault_in_pages fs/gfs2/file.c:784 [inline]
BUG: KASAN: stack-out-of-bounds in gfs2_file_buffered_write+0x505/0x850 fs/gfs2/file.c:1069
Read of size 8 at addr ffffc90003187d30 by task syz.3.4/3655

CPU: 1 PID: 3655 Comm: syz.3.4 Not tainted 5.15.168-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 print_address_description+0x63/0x3b0 mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:434 [inline]
 kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
 should_fault_in_pages fs/gfs2/file.c:784 [inline]
 gfs2_file_buffered_write+0x505/0x850 fs/gfs2/file.c:1069
 gfs2_file_write_iter+0x4a2/0xf10 fs/gfs2/file.c:1165
 call_write_iter include/linux/fs.h:2174 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0xacd/0xe50 fs/read_write.c:594
 ksys_write+0x1a2/0x2c0 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ee851fff9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8ee6998038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8ee86d7f80 RCX: 00007f8ee851fff9
RDX: 0000000000000012 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007f8ee8592296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f8ee86d7f80 R15: 00007ffc51fe14d8
 </TASK>


addr ffffc90003187d30 is located in stack of task syz.3.4/3655 at offset 48 in frame:
 vfs_write+0x0/0xe50

this frame has 3 objects:
 [32, 48) 'iov.i'
 [64, 112) 'kiocb.i'
 [144, 184) 'iter.i'

Memory state around the buggy address:
 ffffc90003187c00: 00 00 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00
 ffffc90003187c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90003187d00: f1 f1 f1 f1 00 00 f2 f2 00 00 00 00 00 00 f2 f2
                                     ^
 ffffc90003187d80: f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3 00 00 00 00
 ffffc90003187e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================