[moderation] [fs?] WARNING in quota_release_workfn

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 27cc6fdf7201 Merge tag 'linux_kselftest-fixes-6.12-rc2' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105bcd27980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f8af0b3195caed62
dashboard link: https://syzkaller.appspot.com/bug?extid=d5395e83299bdfb7ea75
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/87f1d994309a/disk-27cc6fdf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9c7ccdaf7e44/vmlinux-27cc6fdf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7dc828e4bf0e/bzImage-27cc6fdf.xz

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

(kworker/u8:8,2577,1):ocfs2_release_dquot:795 ERROR: status = -30
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2577 at fs/quota/dquot.c:825 quota_release_workfn+0x57b/0x650 fs/quota/dquot.c:825
Modules linked in:
CPU: 1 UID: 0 PID: 2577 Comm: kworker/u8:8 Not tainted 6.12.0-rc1-syzkaller-00306-g27cc6fdf7201 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events_unbound quota_release_workfn
RIP: 0010:quota_release_workfn+0x57b/0x650 fs/quota/dquot.c:825
Code: 28 00 74 08 4c 89 f7 e8 63 57 c9 ff 4c 8b 7c 24 60 4d 39 f7 0f 84 8b 00 00 00 e8 00 c9 62 ff e9 fb fb ff ff e8 f6 c8 62 ff 90 <0f> 0b 90 e9 2d fc ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 05 fc
RSP: 0018:ffffc90009ae7ae0 EFLAGS: 00010293
RAX: ffffffff82320d2a RBX: 0000000000000001 RCX: ffff88802df8bc00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90009ae7bb0 R08: ffffffff82320953 R09: 1ffff1100bdbbc62
R10: dffffc0000000000 R11: ffffed100bdbbc63 R12: ffff88805edde330
R13: dffffc0000000000 R14: ffffc90009ae7b40 R15: ffff88805edde220
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055557e479648 CR3: 0000000022f04000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.