From: syzbot <syzbot+35f4d916c623118d576e@syzkaller.appspotmail.com>
To: Thinh.Nguyen@synopsys.com, andreyknvl@google.com,
dianders@chromium.org, gregkh@linuxfoundation.org,
jflat@chromium.org, kai.heng.feng@canonical.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
malat@debian.org, mathias.nyman@linux.intel.com,
nsaenzjulienne@suse.de, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in usb_reset_and_verify_device
Date: Wed, 04 Sep 2019 07:59:01 -0700 [thread overview]
Message-ID: <00000000000003f6410591bb7223@google.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1909041038340.1722-100000@iolanthe.rowland.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+35f4d916c623118d576e@syzkaller.appspotmail.com
Tested on:
commit: eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git
kernel config: https://syzkaller.appspot.com/x/.config?x=d0c62209eedfd54e
dashboard link: https://syzkaller.appspot.com/bug?extid=35f4d916c623118d576e
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=11d694d6600000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-09-04 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 12:08 KASAN: slab-out-of-bounds Read in usb_reset_and_verify_device syzbot
2019-09-03 19:03 ` Alan Stern
2019-09-03 19:20 ` syzbot
2019-09-03 19:33 ` Alan Stern
2019-09-03 19:58 ` syzbot
2019-09-03 20:58 ` Alan Stern
2019-09-03 21:13 ` syzbot
2019-09-04 14:41 ` Alan Stern
2019-09-04 14:59 ` syzbot [this message]
2019-09-04 15:01 ` Andrey Konovalov
2019-09-04 15:23 ` Alan Stern
2019-09-04 15:56 ` [PATCH] USB: usbcore: Fix slab-out-of-bounds bug during device reset Alan Stern
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=00000000000003f6410591bb7223@google.com \
--to=syzbot+35f4d916c623118d576e@syzkaller.appspotmail.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andreyknvl@google.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jflat@chromium.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=malat@debian.org \
--cc=mathias.nyman@linux.intel.com \
--cc=nsaenzjulienne@suse.de \
--cc=stern@rowland.harvard.edu \
--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).