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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 590b221ed425 Add linux-next specific files for 20250912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f5b642580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12a1d1f3a8199632
dashboard link: https://syzkaller.appspot.com/bug?extid=0e74bb3904b1775045a8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.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/63a963fc26db/disk-590b221e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0c2013d30830/vmlinux-590b221e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7ee4d3a8e8f6/bzImage-590b221e.xz

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

------------[ cut here ]------------
WARNING: fs/quota/dquot.c:829 at quota_release_workfn+0x541/0x610 fs/quota/dquot.c:829, CPU#1: kworker/u8:7/1151
Modules linked in:

CPU: 1 UID: 0 PID: 1151 Comm: kworker/u8:7 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: quota_events_unbound quota_release_workfn

RIP: 0010:quota_release_workfn+0x541/0x610 fs/quota/dquot.c:829
Code: dc 99 e8 32 d1 a8 02 48 8b 5c 24 40 48 8d 44 24 40 48 39 c3 0f 84 89 00 00 00 e8 4a e3 66 ff e9 ef fb ff ff e8 40 e3 66 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:ffffc90003ddf9a0 EFLAGS: 00010293
RAX: ffffffff8258d830 RBX: ffff88805abf0e20 RCX: ffff8880271ebc80
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc90003ddfa50 R08: ffff88805abf0f13 R09: 1ffff1100b57e1e2
R10: dffffc0000000000 R11: ffffed100b57e1e3 R12: 0000000000000020
R13: dffffc0000000000 R14: 0000000000000002 R15: 1ffff1100b57e1e6
FS: 0000000000000000(0000) GS:ffff888125ae8000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f98ed000020 CR3: 000000007d9fa000 CR4: 00000000003526f0
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 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