public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7a2ba6b7b66340cff225@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, rpthibeault@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_bh
Date: Thu, 25 Sep 2025 12:44:03 -0700	[thread overview]
Message-ID: <68d59b83.050a0220.25d7ab.0063.GAE@google.com> (raw)
In-Reply-To: <aNV1BSMAPsx_oKiH@rpthibeault-XPS-13-9305>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+7a2ba6b7b66340cff225@syzkaller.appspotmail.com
Tested-by: syzbot+7a2ba6b7b66340cff225@syzkaller.appspotmail.com

Tested on:

commit:         4ff71af0 Merge tag 'net-6.17-rc8' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a71d34580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8cf2d8760d8941fb
dashboard link: https://syzkaller.appspot.com/bug?extid=7a2ba6b7b66340cff225
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=146ab4e2580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-09-25 19:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aNV1BSMAPsx_oKiH@rpthibeault-XPS-13-9305>
2025-09-25 19:44 ` syzbot [this message]
     [not found] <aOv1RisRR1z1JJ1M@rpthibeault-XPS-13-9305>
2025-10-12 19:36 ` [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_bh syzbot
2024-11-05 13:32 Suraj Sonawane
2024-11-05 21:34 ` syzbot
     [not found] <20240910071417.7632-1-almaz.alexandrovich@paragon-software.com>
2024-09-10  8:09 ` syzbot
  -- strict thread matches above, loose matches on Subject: below --
2024-09-01 20:28 syzbot
2024-09-04 15:47 ` 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=68d59b83.050a0220.25d7ab.0063.GAE@google.com \
    --to=syzbot+7a2ba6b7b66340cff225@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpthibeault@gmail.com \
    --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