From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f72.google.com (mail-oo1-f72.google.com [209.85.161.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 07DE8428494 for ; Wed, 4 Feb 2026 19:15:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.72 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770232503; cv=none; b=gfIhLmWgKNPglkdGCln5gPsg8HmkaBPPz0djJYKLee8CMALF6ViTGgn0QXfHz7+noKZZMTy/uehf4T+bTwQ44V2mAJg+ODdPwc9AjjVvCQaEZoGwNUT/t1l+7iEyeG8ZaRqioNGgxWVUs0PWuLKC5dRGA/4iBCrZ6PsEoHhS8Sk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770232503; c=relaxed/simple; bh=A7kutHE6BxM+sYjbi6vo9dMc/fEDEZYAbvNqDcXDDzI=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=NZRKXeHNqD8J22zCY3HpH+FKceNeuh2JqZbValol4tGxE7BnkO1p60nPGyiG6UNh4sLpb+LNd9qdI4PQWL6NUZ02dbpvyterl/OZrVygF91JgC49H4NPLVhDJ7Ke/bOmejtpWb4sh1Jt/D7hxGe7qkJJoFasolRDWx9tfVaixOE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.72 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f72.google.com with SMTP id 006d021491bc7-662ca3cb667so308002eaf.2 for ; Wed, 04 Feb 2026 11:15:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770232502; x=1770837302; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=JEommf8qicFYiUEwjDjduiXwOibTNcBfvlVDdiq/4tk=; b=wSOM0vX5SaRWC8kTtjagEGw1MBNGAvR8amKepjRI5ZTXYmALanIB1wKkWCPkRy54EG i67H6FNcDkYEo1Z0nN6Z2nmV5t4F8ywdn2FK/Tv8F18WkLLyGmMoRPVC77/YY3M4XsSD l7001LwSE5zqkfGhDomPgD0NC1swOyvjSq/qv7T9kxlLcOjWP63AgzuVtGsQVXT6qspY P2M/4azLugM5ZW0OkMKj6i7bwWOpbJ7CGLOGygbukXUZ6ZMT3xLh9saKi0N37tgmQ4DM DVHlggi360iN9GJPaF0A3xmtH34PSenk3NfKCkkKr8+T24CipmgDdnm4L3Sz220Yatfp 2yog== X-Forwarded-Encrypted: i=1; AJvYcCX4VApvvUSPhy39yOnkCrmhDAVzut7kz1omWwyaEkBYGGmOByIgR9kQy5mVvBiCdlrCLOe9m0rHtmClzxU=@vger.kernel.org X-Gm-Message-State: AOJu0Ywaax292wWhzl9F8FpNYK7raGxnPP7FbyjvbZvDz+BAZdGI727K ioxh3NPo4gk1SS1NrobXDTkD2h4hk6MwlioDgA2XugXcwwwEOciiFOs6NZmsz2tpAGtWMRv/Uw3 y0WzvRYtWxv9gMbnF5UMcjTp1NwAiuR0UR9mIDp9CmugIQ7wMSsjPbyErz1Q= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:88f:b0:662:f6b4:8c53 with SMTP id 006d021491bc7-66a22692691mr1727593eaf.43.1770232502046; Wed, 04 Feb 2026 11:15:02 -0800 (PST) Date: Wed, 04 Feb 2026 11:15:02 -0800 In-Reply-To: X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69839ab6.a00a0220.34fa92.0013.GAE@google.com> Subject: Re: [syzbot] [gfs2?] memory leak in __kthread_create_on_node From: syzbot To: agruenba@redhat.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" 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.