From: syzbot <syzbot+e57495fb65020ac7bca4@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [gfs2?] memory leak in gfs2_quota_init (2)
Date: Wed, 04 Feb 2026 08:58:40 -0800 [thread overview]
Message-ID: <69837ac0.a00a0220.34fa92.0011.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 283073725700 Merge tag 'riscv-for-linus-6.19-rc8' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=108d3c5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d7d0fbecb37bff8
dashboard link: https://syzkaller.appspot.com/bug?extid=e57495fb65020ac7bca4
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=158fa72a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=174c9644580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/29ae0baa9654/disk-28307372.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc5f836cdf79/vmlinux-28307372.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c40c2fb29195/bzImage-28307372.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/bb1679f271de/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=170d3c5a580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e57495fb65020ac7bca4@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88810e866000 (size 8192):
comm "syz.0.477", pid 7931, jiffies 4295008793
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 8429a099):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__do_kmalloc_node mm/slub.c:5656 [inline]
__kmalloc_noprof+0x465/0x680 mm/slub.c:5669
kmalloc_noprof include/linux/slab.h:961 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
gfs2_quota_init+0xe5/0x820 fs/gfs2/quota.c:1409
gfs2_make_fs_rw+0x7a/0xe0 fs/gfs2/super.c:149
gfs2_fill_super+0xfbb/0x1210 fs/gfs2/ops_fstype.c:1275
get_tree_bdev_flags+0x1c0/0x290 fs/super.c:1691
gfs2_get_tree+0x26/0xd0 fs/gfs2/ops_fstype.c:1332
vfs_get_tree+0x30/0x120 fs/super.c:1751
fc_mount fs/namespace.c:1199 [inline]
do_new_mount_fc fs/namespace.c:3636 [inline]
do_new_mount fs/namespace.c:3712 [inline]
path_mount+0x5a9/0x1350 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a3/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
---
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@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 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
next reply other threads:[~2026-02-04 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 16:58 syzbot [this message]
2026-02-05 6:31 ` [syzbot] [gfs2?] memory leak in gfs2_quota_init (2) Qing Wang
2026-02-05 8:41 ` syzbot
2026-02-05 9:06 ` Qing Wang
2026-02-05 9:36 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69837ac0.a00a0220.34fa92.0011.GAE@google.com \
--to=syzbot+e57495fb65020ac7bca4@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.