From: Andrey Konovalov <andreyknvl@google.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.com>,
syzbot <syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Alexander Potapenko <glider@google.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: KMSAN: kernel-usb-infoleak in pcan_usb_pro_send_req
Date: Tue, 6 Aug 2019 16:00:34 +0200 [thread overview]
Message-ID: <CAAeHK+zsz4-rdYt92Ywo1SV+LOsmPY3nF97bGt7j7w8VneAP3g@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1908060957420.1571-100000@iolanthe.rowland.org>
On Tue, Aug 6, 2019 at 3:59 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Tue, 6 Aug 2019, Andrey Konovalov wrote:
>
> > On Tue, Aug 6, 2019 at 2:45 PM Oliver Neukum <oneukum@suse.com> wrote:
> > >
> > > Am Dienstag, den 30.07.2019, 02:38 -0700 schrieb syzbot:
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD commit: 41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> > > > git tree: kmsan
> > > > console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> > > > kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> > > > dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> > > > compiler: clang version 9.0.0 (/home/glider/llvm/clang
> > > > 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> > > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> > > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
> > > >
> > > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > > Reported-by: syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com
> > >
> > > #syz test: https://github.com/google/kasan.git 41550654
> >
> > Hi Oliver,
> >
> > For KMSAN bugs you'll need to use the kmsan tree (syz test:
> > https://github.com/google/kmsan.git COMMIT_ID). I've updated the
> > testing instructions some time ago to reflect this. Sorry for the
> > complexity, this is caused by USB fuzzing and KMSAN not being upstream
> > yet.
>
> Maybe you can fix the "git tree:" header in the bug report. It should
> say "https://github.com/google/kmsan.git" instead of just "kmsan".
Makes sense, will do, thanks!
>
> Alan Stern
>
next prev parent reply other threads:[~2019-08-06 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 9:38 KMSAN: kernel-usb-infoleak in pcan_usb_pro_send_req syzbot
2019-07-30 14:17 ` Alan Stern
2019-07-30 14:20 ` Andrey Konovalov
2019-07-30 14:22 ` Andrey Konovalov
2019-07-30 14:28 ` Alexander Potapenko
2019-08-06 12:45 ` Oliver Neukum
2019-08-06 12:45 ` syzbot
2019-08-06 12:49 ` Andrey Konovalov
2019-08-06 13:59 ` Alan Stern
2019-08-06 14:00 ` Andrey Konovalov [this message]
2019-08-06 13:05 ` Oliver Neukum
2019-08-06 14:44 ` 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=CAAeHK+zsz4-rdYt92Ywo1SV+LOsmPY3nF97bGt7j7w8VneAP3g@mail.gmail.com \
--to=andreyknvl@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).