All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3)
Date: Thu, 18 Sep 2025 12:35:06 -0700	[thread overview]
Message-ID: <68cc5eea.050a0220.28a605.000c.GAE@google.com> (raw)
In-Reply-To: <68cb3c62.050a0220.50883.002b.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3)
Author: sidharthseela@gmail.com

Signed-off-by: Sidharth Seela <sidharthseela@gmail.com>
Reported-by: syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com

#syz test
diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
index 1bf2a6593dec..3c44af1af9a0 100644
--- a/fs/ntfs3/index.c
+++ b/fs/ntfs3/index.c
@@ -718,7 +718,7 @@ static struct NTFS_DE *hdr_find_e(const struct ntfs_index *indx,
 				  const struct INDEX_HDR *hdr, const void *key,
 				  size_t key_len, const void *ctx, int *diff)
 {
-	struct NTFS_DE *e, *found = NULL;
+	struct NTFS_DE *e = NULL, *found = NULL;
 	NTFS_CMP_FUNC cmp = indx->cmp;
 	int min_idx = 0, mid_idx, max_idx = 0;
 	int diff2;
-- 
2.47.3


  reply	other threads:[~2025-09-18 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 22:55 [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3) syzbot
2025-09-18 19:35 ` syzbot [this message]
2025-09-22 18:03 ` Forwarded: " syzbot
2025-10-26 15:54 ` Forwarded: syzbot
2025-10-29 20:03 ` Forwarded: Re: KMSAN: uninit-value in ntfs_read_hdr (3) syzbot
2025-11-05  7:52 ` 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=68cc5eea.050a0220.28a605.000c.GAE@google.com \
    --to=syzbot+332bd4e9d148f11a87dc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.