[v5.15] WARNING in xfs_qm_dqget_cache_insert

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=107eb5ee280000
kernel config: https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link: https://syzkaller.appspot.com/bug?extid=3902b288d4b020197b50
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fcba29280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175634b1280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65d6c2ec328/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf811ebac37b/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2f32fdecf97/bzImage-9d6bde85.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e93386fea47d/mount_0.gz

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

RBP: 00007fff851768f0 R08: 0000000000000001 R09: 00007fff85176900
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007fff85176930 R14: 00007fff85176910 R15: 0000000000000003
</TASK>
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3527 at fs/xfs/xfs_dquot.c:828 xfs_qm_dqget_cache_insert+0x101/0x110
Modules linked in:
CPU: 1 PID: 3527 Comm: syz-executor264 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:xfs_qm_dqget_cache_insert+0x101/0x110 fs/xfs/xfs_dquot.c:828
Code: 38 c1 7c a2 48 89 ef e8 dd 28 b7 fe eb 98 44 89 e1 80 e1 07 80 c1 03 38 c1 7c a8 4c 89 e7 e8 56 28 b7 fe eb 9e e8 df cc 6d fe <0f> 0b eb b8 66 2e 0f 1f 84 00 00 00 00 00 90 55 41 56 53 48 89 fb
RSP: 0018:ffffc90002ddf7b0 EFLAGS: 00010293
RAX: ffffffff83121c01 RBX: 000000000000ee00 RCX: ffff88801fce1dc0
RDX: 0000000000000000 RSI: ffffffff8cd19160 RDI: 00000000fffffff4
RBP: ffff88801e9c86a0 R08: 0000000000000005 R09: ffffffff83121b48
R10: 0000000000000002 R11: ffff88801fce1dc0 R12: ffff88801d9c6000
R13: dffffc0000000000 R14: ffff88801d9c60f0 R15: 00000000fffffff4
FS: 00005555572f1300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557fa699e0e8 CR3: 0000000074e52000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
xfs_qm_dqget+0x2af/0x4e0 fs/xfs/xfs_dquot.c:901
xfs_qm_vop_dqalloc+0x5a9/0xee0 fs/xfs/xfs_qm.c:1683
xfs_setattr_nonsize+0x2e9/0xc40 fs/xfs/xfs_iops.c:709
xfs_vn_setattr+0x2f7/0x340 fs/xfs/xfs_iops.c:1050
notify_change+0xd4d/0x1000 fs/attr.c:488
chown_common+0x592/0x890 fs/open.c:680
vfs_fchown fs/open.c:748 [inline]
ksys_fchown+0xde/0x150 fs/open.c:759
__do_sys_fchown fs/open.c:767 [inline]
__se_sys_fchown fs/open.c:765 [inline]
__x64_sys_fchown+0x76/0x80 fs/open.c:765
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1df590fa79
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 00 00 90 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff851768c8 EFLAGS: 00000246 ORIG_RAX: 000000000000005d
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f1df590fa79
RDX: 0000000000000000 RSI: 000000000000ee00 RDI: 0000000000000003
RBP: 00007fff851768f0 R08: 0000000000000001 R09: 00007fff85176900
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007fff85176930 R14: 00007fff85176910 R15: 0000000000000003
</TASK>


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

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

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

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

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit 8dc9384b7d75012856b02ff44c37566a55fc2abf
git tree: upstream
Author: Dave Chinner <dchi...@redhat.com>
Date: Wed Jan 5 01:22:18 2022 +0000

xfs: reduce kvmalloc overhead for CIL shadow buffers

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10ea56aae80000

kernel config: https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link: https://syzkaller.appspot.com/bug?extid=3902b288d4b020197b50

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fcba29280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175634b1280000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection