[moderation] [fs?] WARNING in quota_release_workfn (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 44982d352c33 Add linux-next specific files for 20260219
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17bf495a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cdf9388b212a2b28
dashboard link: https://syzkaller.appspot.com/bug?extid=5aada8d5222217d4ce48
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
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/20e5984faec2/disk-44982d35.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4a42482739ac/vmlinux-44982d35.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1c6b6cee1069/bzImage-44982d35.xz

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

------------[ cut here ]------------
atomic_read(&dquot->dq_count)
WARNING: fs/quota/dquot.c:829 at quota_release_workfn+0x549/0x620 fs/quota/dquot.c:829, CPU#0: kworker/u8:14/7931
Modules linked in:
CPU: 0 UID: 0 PID: 7931 Comm: kworker/u8:14 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: quota_events_unbound quota_release_workfn
RIP: 0010:quota_release_workfn+0x549/0x620 fs/quota/dquot.c:829
Code: 35 9a e8 ba fd 81 02 48 8b 5c 24 40 48 8d 44 24 40 48 39 c3 0f 84 89 00 00 00 e8 62 12 5d ff e9 ef fb ff ff e8 58 12 5d ff 90 <0f> 0b 90 e9 24 fc ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c f8
RSP: 0018:ffffc9000d237a80 EFLAGS: 00010293
RAX: ffffffff82689038 RBX: ffff88807bda1620 RCX: ffff888027590000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc9000d237b30 R08: ffff88807bda1713 R09: 1ffff1100f7b42e2
R10: dffffc0000000000 R11: ffffed100f7b42e3 R12: 0000000000000020
R13: dffffc0000000000 R14: 0000000000000002 R15: 1ffff1100f7b42e6
FS: 0000000000000000(0000) GS:ffff888125457000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7128d51bd3 CR3: 000000007b0b6000 CR4: 00000000003526f0
Call Trace:
<TASK>
process_one_work+0x949/0x1650 kernel/workqueue.c:3279
process_scheduled_works kernel/workqueue.c:3362 [inline]
worker_thread+0xb46/0x1140 kernel/workqueue.c:3443
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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