linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com>
To: glider@google.com, gregkh@linuxfoundation.org,
	gustavo@embeddedor.com, linux-usb@vger.kernel.org,
	oneukum@suse.com, syzkaller-bugs@googlegroups.com
Subject: Re: KMSAN: kernel-usb-infoleak in pcan_usb_pro_send_req
Date: Tue, 06 Aug 2019 07:44:00 -0700	[thread overview]
Message-ID: <000000000000f400cd058f73dadd@google.com> (raw)
In-Reply-To: <1565096744.8136.23.camel@suse.com>

Hello,

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

Reported-and-tested-by:  
syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com

Tested on:

commit:         41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
git tree:       https://github.com/google/kmsan.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
compiler:       clang version 9.0.0 (/home/glider/llvm/clang  
80fee25776c2fb61e74c1ecb1a523375c2500b69)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1170f88c600000

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

      reply	other threads:[~2019-08-06 14:44 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
2019-08-06 13:05 ` Oliver Neukum
2019-08-06 14:44   ` syzbot [this message]

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=000000000000f400cd058f73dadd@google.com \
    --to=syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com \
    --cc=glider@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.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).