[syzbot] [ocfs2?] WARNING in dqput

From: syzbot
Date: Wed Jan 01 2025 - 03:23:32 EST


Hello,

syzbot found the following issue on:

HEAD commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=149256df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c541fa8af5c9cc7
dashboard link: https://syzkaller.appspot.com/bug?extid=bf75d2e9b63fe9e0c330
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e5d818580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0ebebb2cf79b/disk-ccb98cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8da8041cbc40/vmlinux-ccb98cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8de730af73c0/bzImage-ccb98cce.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6b4af5111ec5/mount_3.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bf75d2e9b63fe9e0c330@xxxxxxxxxxxxxxxxxxxxxxxxx

------------[ cut here ]------------
WARNING: CPU: 0 PID: 9 at fs/quota/dquot.c:880 dqput+0x359/0x490 fs/quota/dquot.c:880
Modules linked in:
CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #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:880
Code: f7 64 ff eb 05 e8 87 f7 64 ff 48 c7 c7 80 58 61 8e 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 6d ef 90 09 e8 68 f7 64 ff 90 <0f> 0b 90 e9 5b fe ff ff 48 c7 c1 2c b1 19 90 80 e1 07 80 c1 03 38
RSP: 0018:ffffc900000e7af0 EFLAGS: 00010293
RAX: ffffffff823a7c78 RBX: ffff888060092c00 RCX: ffff88801c2b0000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 1ffff1100c012584 R08: ffffffff823a79bc R09: 1ffff1100c0125a2
R10: dffffc0000000000 R11: ffffed100c0125a3 R12: 1ffff1100c0125a2
R13: dffffc0000000000 R14: ffff888060092d10 R15: ffff888060092c20
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a980c62a18 CR3: 0000000032178000 CR4: 0000000000350ef0
Call Trace:
<TASK>
dquot_scan_active+0x156/0x280 fs/quota/dquot.c:644
qsync_work_fn+0xa9/0x150 fs/ocfs2/quota_global.c:658
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa68/0x1840 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f2/0x390 kernel/kthread.c:389
ret_from_fork+0x4d/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 syzkaller@xxxxxxxxxxxxxxxx.

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 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 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