From: syzbot <syzbot+06283a66a648cd073885@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, hverkuil@xs4all.nl,
j.vosburgh@gmail.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, maheshb@google.com,
mchehab@kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vfalico@gmail.com
Subject: Re: INFO: task hung in vivid_stop_generating_vid_cap
Date: Fri, 22 Mar 2019 00:08:00 -0700 [thread overview]
Message-ID: <000000000000e626290584a983c0@google.com> (raw)
In-Reply-To: <00000000000080601805795ada2e@google.com>
syzbot has bisected this bug to:
commit 4493b81bea24269df898339dee638d7c5cb2b2df
Author: Mahesh Bandewar <maheshb@google.com>
Date: Wed Mar 8 18:55:54 2017 +0000
bonding: initialize work-queues during creation of bond
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176d1617200000
start commit: 4493b81b bonding: initialize work-queues during creation o..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14ed1617200000
console output: https://syzkaller.appspot.com/x/log.txt?x=10ed1617200000
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
Reported-by: syzbot+06283a66a648cd073885@syzkaller.appspotmail.com
Fixes: 4493b81bea24 ("bonding: initialize work-queues during creation of
bond")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-22 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 9:40 INFO: task hung in vivid_stop_generating_vid_cap syzbot
2018-10-29 16:22 ` syzbot
2019-03-22 7:08 ` syzbot [this message]
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
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=000000000000e626290584a983c0@google.com \
--to=syzbot+06283a66a648cd073885@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=hverkuil@xs4all.nl \
--cc=j.vosburgh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maheshb@google.com \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.