From nobody Sat Feb 7 15:11:20 2026 Received: from mail-oi1-f199.google.com (mail-oi1-f199.google.com [209.85.167.199]) (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 13E40353EEE for ; Fri, 23 Jan 2026 05:12:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.199 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769145160; cv=none; b=jQpG1pxiCBYrxS5u2XgGwB7O0I5WeurOG50gBC8pAlbpLxiAPbgdEkpShFuEwvBwbZh0XY3dPYihGePr1oRgTPLGLz9DYodiEeZD2WTSgfuTIKZVkarEsDa2+IqeLPOfjioyxNkiL2k7HM2PUJMYZeGQSS0ytbtb99DnNwk2JGU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769145160; c=relaxed/simple; bh=MtPbCStyoUXOSvo946CpM93eRkQhKYRJUREZlxA3Gro=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=YHOmufLOQgmIyOKG3V2HoHOKDmbwJ+/T6G+XzNWgMVeZeyXdF7fJ8QfCkQJCrsBAalsPrQ34WgESiRHad/83gmK9EJlSoxaqxd44K9wcT7JoOpJgDXHSWLpqo58dz9W92uTC4b6C6SY9X1Dpl5WusyNyrn4kVmymVvzhHIRBQow= 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.167.199 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-oi1-f199.google.com with SMTP id 5614622812f47-45c7dc03e6dso2770905b6e.1 for ; Thu, 22 Jan 2026 21:12:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769145153; x=1769749953; 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=NN3HTO6KzrxUm2hR/kyt7kJxBloXi4tx3KUgUl5VvFc=; b=nPy+TEzUQOngTMwaLPkgvqkcud9470jHP25Ezlkwo4tnIqSkix7vPtz7r7L5cJuuoq kAO8HQl6u1grOqGv1zu5/UOxMp8zEuSK0oelp9HH30MxcSb8TwiDWQlzKQzQ4iG8JClD f2KxhhyVmlP0mZjEHAQjaTdOTfjvkmoqSM0JOmkA9wGCc1i6+ykxrQbXw9NqRg5rO8Aq QK5R2a1+MezzZSX5VPKtCavSGj7Pb4yGdLcgqNuDZW70zkJHQqWXx70L+OiLcARC+PVU USIBXVYAYa2Uf+8gpu8j82VAaJP7QcTeWSTy525bPw0QsNcMOrbJsHcdxtYvyB9Wb4o0 i4Wg== X-Gm-Message-State: AOJu0YzcMWfqm2jmvG6/XPDRyfxnY6lsg12r3l3/WN2lYoTsUocwvfBA fj1cyqoia8zh1BTiFxVuJEd/RWI8hsvTUN925rlscb7FFdNfGPzTcy8EoL5/JZ885gW29+34Ehe Il4V4P+8Lz8RJbELnQopIRHMtYYR2u1IFWGekiUWNo3NBbeaxKSeXX5QahW8= 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:f07:b0:662:c854:6bc2 with SMTP id 006d021491bc7-662caaebaf2mr844582eaf.13.1769145152954; Thu, 22 Jan 2026 21:12:32 -0800 (PST) Date: Thu, 22 Jan 2026 21:12:32 -0800 In-Reply-To: <69727142.050a0220.706b.0027.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69730340.a70a0220.35de72.0004.GAE@google.com> Subject: Forwarded: [PATCH] jfs: fix KMSAN warning in txLock 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] jfs: fix KMSAN warning in txLock Author: kartikey406@gmail.com #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git= master Syzbot reported a KMSAN uninit-value warning in txLock when accessing jfs_ip->atlhead: BUG: KMSAN: uninit-value in txLock+0x13a2/0x2900 fs/jfs/jfs_txnmgr.c:659 This occurs because the jfs_inode_info structure is allocated from a slab cache but not fully initialized, leaving fields like atlhead, atltail, and anon_inode_list with garbage values from previously freed inodes. When txLock() attempts to traverse the anonymous transaction lock list by reading jfs_ip->atlhead, it accesses uninitialized memory, triggering the KMSAN warning. Fix this by zeroing the entire jfs_inode_info structure in jfs_alloc_inode(). This is consistent with how other filesystems handle inode allocation and ensures all fields start with known values, preventing this and potential similar bugs. Reported-by: syzbot+d3a57c32b9112d7b01ec@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=3Dd3a57c32b9112d7b01ec Signed-off-by: Deepanshu Kartikey --- fs/jfs/super.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/fs/jfs/super.c b/fs/jfs/super.c index 3cfb86c5a36e..236fe8d42542 100644 --- a/fs/jfs/super.c +++ b/fs/jfs/super.c @@ -105,9 +105,7 @@ static struct inode *jfs_alloc_inode(struct super_block= *sb) jfs_inode =3D alloc_inode_sb(sb, jfs_inode_cachep, GFP_NOFS); if (!jfs_inode) return NULL; -#ifdef CONFIG_QUOTA - memset(&jfs_inode->i_dquot, 0, sizeof(jfs_inode->i_dquot)); -#endif + memset(jfs_inode, 0, sizeof(struct jfs_inode_info)); return &jfs_inode->vfs_inode; } =20 --=20 2.43.0