From: syzbot <syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] [mm?] KMSAN: kernel-infoleak in hugetlbfs_read_iter
Date: Tue, 11 Nov 2025 18:28:02 -0800 [thread overview]
Message-ID: <6913f0b2.a70a0220.22f260.0155.GAE@google.com> (raw)
In-Reply-To: <20251112012749.2082979-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com
Tested-by: syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com
Tested on:
commit: 24172e0d Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=107bdc12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cbf50e713aaa5cb0
dashboard link: https://syzkaller.appspot.com/bug?extid=f64019ba229e3a5c411b
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=12858914580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-12 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251112012749.2082979-1-kartikey406@gmail.com>
2025-11-12 2:28 ` syzbot [this message]
[not found] <20251112124054.2318311-1-kartikey406@gmail.com>
2025-11-12 14:33 ` [syzbot] [fs?] [mm?] KMSAN: kernel-infoleak in hugetlbfs_read_iter syzbot
[not found] <20251112005422.2038252-1-kartikey406@gmail.com>
2025-11-12 1:25 ` syzbot
2025-11-10 18:09 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=6913f0b2.a70a0220.22f260.0155.GAE@google.com \
--to=syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox