From: Alan Stern <stern@rowland.harvard.edu>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: syzbot <syzbot+c7b0ec009a216143df30@syzkaller.appspotmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Souptick Joarder <jrdr.linux@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
<linux-media@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Richard Fontana <rfontana@redhat.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: KASAN: use-after-free Read in usbvision_v4l2_open
Date: Tue, 10 Dec 2019 15:13:28 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1912101508470.1647-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <CAAeHK+wY+35uBvr0=FnKsWOj91QhXuVE++V7frn5AihAPLvo5Q@mail.gmail.com>
On Tue, 10 Dec 2019, Andrey Konovalov wrote:
> On Tue, Dec 10, 2019 at 8:48 PM Alan Stern <stern@rowland.harvard.edu> wrote:
> > This looks like a race in v4l2_open(): The function drops the
> > videodev_lock mutex before calling the video driver's open routine, and
> > the device can be unregistered during the short time between.
> >
> > This patch tries to make the race much more likely to happen, for
> > testing and verification.
> >
> > Andrey, will syzbot run the same test with this patch, even though it
> > says it doesn't have a reproducer?
>
> Hi Alan,
>
> No, unfortunately there's nothing to run if there's no reproducer.
> It's technically possible to run the same program log that triggered
> the bug initially, but since the bug wasn't reproduced with this log
> even without the patch, there isn't much sense in running it with the
> patch applied.
Actually it does make sense. That bug was caused by a race, and the
patch tries to make the race much more likely to happen, so the same
test should fail again.
But never mind; I'll try a different approach. There's another syzbot
bug report, one with a reproducer, and with this patch in place it
should trigger the same race. I'll try submitting it that way.
By the way, do you know why syzbot sent _two_ reply messages? One with
message ID <00000000000031a0af05995eca0b@google.com> and the other with
message ID <000000000000441a4205995eca11@google.com>? It seems like
overkill.
Alan Stern
next prev parent reply other threads:[~2019-12-10 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 22:15 KASAN: use-after-free Read in usbvision_v4l2_open syzbot
2019-12-10 19:47 ` Alan Stern
2019-12-10 19:48 ` syzbot
2019-12-10 20:17 ` Alan Stern
2019-12-11 14:23 ` Andrey Konovalov
2019-12-11 15:14 ` Alan Stern
2019-12-11 15:35 ` Dmitry Vyukov
2019-12-12 16:52 ` general protection fault in usb_set_interface Alan Stern
2019-12-10 19:48 ` Re: KASAN: use-after-free Read in usbvision_v4l2_open syzbot
2019-12-10 20:06 ` Andrey Konovalov
2019-12-10 20:13 ` Alan Stern [this message]
2019-12-11 14:22 ` Andrey Konovalov
2019-12-11 15:30 ` Dmitry Vyukov
2019-12-11 16:22 ` Alan Stern
2019-12-12 16:08 ` Andrey Konovalov
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=Pine.LNX.4.44L0.1912101508470.1647-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=andreyknvl@google.com \
--cc=hverkuil@xs4all.nl \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfontana@redhat.com \
--cc=syzbot+c7b0ec009a216143df30@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).