From: syzbot <syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KMSAN: kernel-infoleak in iowarrior_read
Date: Sat, 14 Sep 2024 18:54:02 -0700 [thread overview]
Message-ID: <0000000000000d0b3206221ebbc5@google.com> (raw)
In-Reply-To: <20240914203143.99551-1-aha310510@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.com
Tested-by: syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.com
Tested on:
commit: 0babf683 Merge tag 'pinctrl-v6.11-4' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ec6407980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea008021530b2de3
dashboard link: https://syzkaller.appspot.com/bug?extid=b8080cbc8d286a5fa23a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-09-15 1:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 2:05 [syzbot] [usb?] KMSAN: kernel-infoleak in iowarrior_read syzbot
2024-09-12 14:16 ` [syzbot] " syzbot
2024-09-12 14:21 ` Jeongjun Park
2024-09-12 15:47 ` syzbot
2024-09-12 18:47 ` [syzbot] " syzbot
2024-09-14 20:31 ` [syzbot] [usb?] " Jeongjun Park
2024-09-15 1:54 ` syzbot [this message]
2024-09-14 20:32 ` Jeongjun Park
2024-09-15 2:09 ` syzbot
2024-09-15 18:13 ` Jeongjun Park
2024-09-15 18:41 ` syzbot
2024-09-15 18:19 ` Jeongjun Park
2024-09-15 19:05 ` syzbot
[not found] <20240912141621.7782-1-aha310510@gmail.com>
2024-09-12 15:19 ` syzbot
[not found] <20240912184649.92658-1-djahchankoike@gmail.com>
2024-09-12 19:39 ` 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=0000000000000d0b3206221ebbc5@google.com \
--to=syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.com \
--cc=aha310510@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