[moderation] [fs?] WARNING in dqput

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 11a299a7933e Merge tag 'for-6.12/block-20240925' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13738507980000
kernel config: https://syzkaller.appspot.com/x/.config?x=31f49563bb05c4a8
dashboard link: https://syzkaller.appspot.com/bug?extid=67d4637a9e67cef12845
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ja...@suse.com linux-...@vger.kernel.org linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e97035004495/disk-11a299a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0be318a25b1d/vmlinux-11a299a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/91f17271baa3/bzImage-11a299a7.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5265 at fs/quota/dquot.c:879 dqput+0x359/0x490 fs/quota/dquot.c:879
Modules linked in:
CPU: 0 UID: 0 PID: 5265 Comm: kworker/0:6 Not tainted 6.11.0-syzkaller-10669-g11a299a7933e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events qsync_work_fn
RIP: 0010:dqput+0x359/0x490 fs/quota/dquot.c:879
Code: ee 63 ff eb 05 e8 e7 ee 63 ff 48 c7 c7 40 48 61 8e 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 5d a6 94 09 e8 c8 ee 63 ff 90 <0f> 0b 90 e9 5b fe ff ff 48 c7 c1 c8 eb 1b 90 80 e1 07 80 c1 03 38
RSP: 0018:ffffc90004277af0 EFLAGS: 00010293
RAX: ffffffff8230c628 RBX: ffff8880597e8400 RCX: ffff88805c5fbc00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 1ffff1100b2fd084 R08: ffffffff8230c36c R09: 1ffff1100b2fd0a2
R10: dffffc0000000000 R11: ffffed100b2fd0a3 R12: 1ffff1100b2fd0a2
R13: dffffc0000000000 R14: ffff8880597e8510 R15: ffff8880597e8420
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555589b83808 CR3: 000000000e734000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dquot_scan_active+0x156/0x280 fs/quota/dquot.c:645
qsync_work_fn+0xa9/0x150 fs/ocfs2/quota_global.c:658
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</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 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