public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+aac438d7a1c44071e04b@syzkaller.appspotmail.com>
To: agruenba@redhat.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] memory leak in __kthread_create_on_node
Date: Wed, 04 Feb 2026 11:15:02 -0800	[thread overview]
Message-ID: <69839ab6.a00a0220.34fa92.0013.GAE@google.com> (raw)
In-Reply-To: <CAHc6FU6E=3FyN7WvSSydWfE2F_JXXWkfw6A9TD5PXatpp73SVQ@mail.gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in gfs2_trans_begin

BUG: memory leak
unreferenced object 0xffff88812f712360 (size 144):
  comm "syz.3.130", pid 7417, jiffies 4294957464
  hex dump (first 32 bytes):
    fa 02 7a 82 ff ff ff ff 05 00 00 00 00 00 00 00  ..z.............
    0b 00 00 00 00 00 00 00 06 00 00 00 00 00 00 00  ................
  backtrace (crc 643c8b36):
    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]
    kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
    gfs2_trans_begin+0x29/0xa0 fs/gfs2/trans.c:120
    alloc_dinode fs/gfs2/inode.c:432 [inline]
    gfs2_create_inode+0xbfa/0x17f0 fs/gfs2/inode.c:822
    gfs2_atomic_open+0x96/0x190 fs/gfs2/inode.c:1402
    atomic_open fs/namei.c:4304 [inline]
    lookup_open fs/namei.c:4415 [inline]
    open_last_lookups fs/namei.c:4549 [inline]
    path_openat+0x158f/0x20f0 fs/namei.c:4793
    do_filp_open+0x104/0x1f0 fs/namei.c:4823
    do_sys_openat2+0xcb/0x180 fs/open.c:1430
    do_sys_open fs/open.c:1436 [inline]
    __do_sys_open fs/open.c:1444 [inline]
    __se_sys_open fs/open.c:1440 [inline]
    __x64_sys_open+0x7e/0xf0 fs/open.c:1440
    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


Tested on:

commit:         da6f5bbc gfs2: fix memory leaks in gfs2_fill_super err..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1774a402580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9d7d0fbecb37bff8
dashboard link: https://syzkaller.appspot.com/bug?extid=aac438d7a1c44071e04b
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

Note: no patches were applied.

       reply	other threads:[~2026-02-04 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHc6FU6E=3FyN7WvSSydWfE2F_JXXWkfw6A9TD5PXatpp73SVQ@mail.gmail.com>
2026-02-04 19:15 ` syzbot [this message]
     [not found] <CAHc6FU5FACWy-y-t=qEyMsJHSv5D7A9XgYMdxbDh1S0tgz=kQg@mail.gmail.com>
2026-02-04 12:07 ` [syzbot] [gfs2?] memory leak in __kthread_create_on_node syzbot
     [not found] <20260131023756.72030-1-kartikey406@gmail.com>
2026-01-31  5:22 ` syzbot
     [not found] <20260130143741.67498-1-kartikey406@gmail.com>
2026-01-30 15:20 ` syzbot
2026-01-30 14:23 syzbot
2026-02-03 10:01 ` Andreas Gruenbacher
2026-02-03 13:35   ` 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=69839ab6.a00a0220.34fa92.0013.GAE@google.com \
    --to=syzbot+aac438d7a1c44071e04b@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox