From: syzbot <syzbot+06283a66a648cd073885@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, dvyukov@google.com,
hans.verkuil@cisco.com, helen.koike@collabora.com,
hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
j.vosburgh@gmail.com, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
maheshb@google.com, mchehab+samsung@kernel.org,
mchehab@kernel.org, mchehab@s-opensource.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tfiga@chromium.org, vfalico@gmail.com
Subject: Re: INFO: task hung in vivid_stop_generating_vid_cap
Date: Thu, 07 Nov 2019 05:42:06 -0800 [thread overview]
Message-ID: <000000000000c9f0a40596c1d46b@google.com> (raw)
In-Reply-To: <00000000000080601805795ada2e@google.com>
syzbot suspects this bug was fixed by commit:
commit d65842f7126aa1a87fb44b7c9980c12630ed4f33
Author: Hans Verkuil <hverkuil@xs4all.nl>
Date: Mon Nov 19 11:09:00 2018 +0000
media: vb2: add waiting_in_dqbuf flag
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1417a04a600000
start commit: 9f51ae62 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=62118286bb772a24
dashboard link: https://syzkaller.appspot.com/bug?extid=06283a66a648cd073885
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15701a33400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154c8e4d400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: media: vb2: add waiting_in_dqbuf flag
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-07 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000080601805795ada2e@google.com>
2019-03-22 7:08 ` INFO: task hung in vivid_stop_generating_vid_cap syzbot
2019-03-22 8:00 ` Dmitry Vyukov
2019-03-22 8:06 ` Dmitry Vyukov
2019-11-07 18:51 ` Marc Kleine-Budde
2019-03-22 22:45 ` syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-11 14:00 ` Hans Verkuil
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=000000000000c9f0a40596c1d46b@google.com \
--to=syzbot+06283a66a648cd073885@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=hans.verkuil@cisco.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=j.vosburgh@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maheshb@google.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tfiga@chromium.org \
--cc=vfalico@gmail.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).