From nobody Fri Apr 3 02:56:57 2026 Received: from mail-ot1-f72.google.com (mail-ot1-f72.google.com [209.85.210.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 0884130EF68 for ; Tue, 24 Mar 2026 23:34:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.72 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774395281; cv=none; b=UTh++jL2rF3UZA+CUITmcUbCid2WknXceEhDESXAv5rwYhIqF490c9X+v82kcnZX7BW2R/+7p3VikvvjxkHweNfIpBOawByywVn2RSLxY19hluHaDiMQcSpppdvt2ZCq3XaEKunKXZVSAp7Ueg9kT3BSottssj5N9aXG1RB2nfs= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774395281; c=relaxed/simple; bh=PQxSTr5rslG8QR8zVO+yc7JblbeNgcMnwdnp3tbepf4=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=mJUnh8zyNc1vUBzS/qzVZTpO6qozwgjg+l0vDnJ9vLcSf3zE77LR9iZ3oiKUb6EFG52+OH8TZoD9eUURbXFOsDbISgr2puQjge+Ti+TMTnp23y5+KZhpJ7eDqDHS/xi7t1NplA6wNHXkOy+uD1DHjcY7b157T23A0kmMRB5r5RI= 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.210.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-ot1-f72.google.com with SMTP id 46e09a7af769-7d7438fc7f0so15517685a34.0 for ; Tue, 24 Mar 2026 16:34:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774395279; x=1775000079; 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=OAM5psRKkXIUDCvSsukCofCFQUaEx73Um8zRmGNroNU=; b=JTq0MoYfA7EgK8zIhgWdP2ueVHYPFtLuWrnv+SlGhyeigCcWa4yL1uMZAXLkUL1iwc 17OuBbwqSC3mK1zIfGKRIM6T04ZT8VqfSyrCk7wBzP12mj4/B0pVs3q7ofWZoPN5A+mK MJeht8YySyZVeVHDy89f7TOjjzpskLZyJ9JHIuxNhwtO8Z1wTIKc+xyhSprJNz02Snuf upa/X9VnU/8z5SLcj+Y7eEW21MXQSYcSiW+ml2eK9QwZ4HCaXJMXOzvLrA6mKarACf+I /KME85OHx8ugDCyMcVOpkpmMXtDDJuJ0LUFeBCDwJgxYDcn1TXmEVuHx+lX0jG5Q/Eh3 RPvQ== X-Gm-Message-State: AOJu0YyMG+PCBxnNs+UBH2PYUjJncVYW2zJFiKjMyaTcKvi1j+7jB4kR RDV/WQmVsMefuQZLRvZCIIN+THhPnzEeCtTe50DlG5c4XrJUdQj9veXhDdOLYs6lBCnG8E98iUK cfCSj+CaF+5IHk2KFfHQOep9O0XP0ZOPsgcVet6C/aDP/GYJ5+SCSvyp0Q88= 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:1624:b0:67b:f13d:cf9b with SMTP id 006d021491bc7-67dff5a061amr883889eaf.61.1774395278958; Tue, 24 Mar 2026 16:34:38 -0700 (PDT) Date: Tue, 24 Mar 2026 16:34:38 -0700 In-Reply-To: <69c2aff4.050a0220.3bf4de.00b3.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69c31f8e.a70a0220.234938.003a.GAE@google.com> Subject: Forwarded: [PATCH] gfs2: fix missing kmem_cache_destroy() of sd_bufdata in gfs2_kill_sb() From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: [PATCH] gfs2: fix missing kmem_cache_destroy() of sd_bufdata in gf= s2_kill_sb() Author: kartikey406@gmail.com #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gi= t master gfs2_fill_super() creates a per-superblock slab cache for gfs2_bufdata objects with a name derived from the filesystem name: sdp->sd_bufdata =3D kmem_cache_create("gfs2-bufdata/", ...); However, gfs2_kill_sb() does not call kmem_cache_destroy() on this cache during unmount. This means the cache persists after the filesystem is unmounted, and a subsequent mount attempt will try to create a cache with the same name, triggering a warning in kmem_cache_sanity_check(): kmem_cache of name 'gfs2-bufdata/syz:syz' already exists WARNING: mm/slab_common.c:112 The error path in gfs2_fill_super() already handles this correctly via the fail_bufdata label. Add the missing kmem_cache_destroy() call to gfs2_kill_sb() to fix the leak on the normal unmount path. Reported-by: syzbot+b441db1854c360b83221@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=3Db441db1854c360b83221 Signed-off-by: Deepanshu Kartikey --- fs/gfs2/ops_fstype.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c index b44adb40635d..38e4a9dc96bc 100644 --- a/fs/gfs2/ops_fstype.c +++ b/fs/gfs2/ops_fstype.c @@ -1803,7 +1803,7 @@ static void gfs2_kill_sb(struct super_block *sb) set_bit(SDF_KILL, &sdp->sd_flags); gfs2_flush_delete_work(sdp); destroy_workqueue(sdp->sd_delete_wq); - + kmem_cache_destroy(sdp->sd_bufdata); kill_block_super(sb); } =20 --=20 2.43.0