From: syzbot <syzbot+aac438d7a1c44071e04b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [gfs2?] memory leak in __kthread_create_on_node
Date: Wed, 04 Feb 2026 03:39:51 -0800 [thread overview]
Message-ID: <69833007.a00a0220.37c87e.001e.GAE@google.com> (raw)
In-Reply-To: <697cbeda.050a0220.142e72.0000.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [gfs2?] memory leak in __kthread_create_on_node
Author: agruenba@redhat.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git
for-next
next prev parent reply other threads:[~2026-02-04 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 14:23 [syzbot] [gfs2?] memory leak in __kthread_create_on_node syzbot
2026-01-30 14:37 ` Forwarded: [PATCH] gfs2: fix memory leak of kernel threads on mount failure syzbot
2026-01-31 2:38 ` Forwarded: [PATCH] gfs2: fix memory leaks in gfs2_fill_super error path syzbot
2026-02-03 10:01 ` [syzbot] [gfs2?] memory leak in __kthread_create_on_node Andreas Gruenbacher
2026-02-03 13:35 ` syzbot
2026-02-04 11:39 ` syzbot [this message]
2026-02-04 18:54 ` Forwarded: " 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=69833007.a00a0220.37c87e.001e.GAE@google.com \
--to=syzbot+aac438d7a1c44071e04b@syzkaller.appspotmail.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