From: syzbot <syzbot+ea05c832a73d0615bf33@syzkaller.appspotmail.com>
To: ezequiel@collabora.com, hans.verkuil@cisco.com,
hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab+samsung@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, sque@chromium.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in v4l2_release
Date: Wed, 20 Mar 2019 12:40:00 -0700 [thread overview]
Message-ID: <00000000000090e7eb05848bc9b7@google.com> (raw)
In-Reply-To: <0000000000005943f3057acf6a1e@google.com>
syzbot has bisected this bug to:
commit 757fdb51c14fda221ccb6999a865f7f895c79750
Author: Hans Verkuil <hans.verkuil@cisco.com>
Date: Mon May 21 08:54:59 2018 +0000
media: vivid: add request support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=145c3a6d200000
start commit: 757fdb51 media: vivid: add request support
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=165c3a6d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=125c3a6d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
dashboard link: https://syzkaller.appspot.com/bug?extid=ea05c832a73d0615bf33
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b8e6a3400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14e73e2b400000
Reported-by: syzbot+ea05c832a73d0615bf33@syzkaller.appspotmail.com
Fixes: 757fdb51 ("media: vivid: add request support")
prev parent reply other threads:[~2019-03-20 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 22:09 possible deadlock in v4l2_release syzbot
2018-11-17 8:24 ` syzbot
2019-03-20 19:40 ` 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=00000000000090e7eb05848bc9b7@google.com \
--to=syzbot+ea05c832a73d0615bf33@syzkaller.appspotmail.com \
--cc=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sque@chromium.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).