From: syzbot <syzbot+f9966a25169b6d66d61f@syzkaller.appspotmail.com>
To: dafna3@gmail.com, hans.verkuil@cisco.com,
hverkuil-cisco@xs4all.nl, kyungmin.park@samsung.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
m.szyprowski@samsung.com, mchehab+samsung@kernel.org,
mchehab@kernel.org, pawel@osciak.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in vb2_core_reqbufs
Date: Thu, 21 Mar 2019 08:55:00 -0700 [thread overview]
Message-ID: <000000000000b87c6405849cc2d6@google.com> (raw)
In-Reply-To: <00000000000069922505797781b0@google.com>
syzbot has bisected this bug to:
commit 3b15f68e19c28a76d175f61943a8c23224afce93
Author: Dafna Hirschfeld <dafna3@gmail.com>
Date: Mon Jan 21 11:46:18 2019 +0000
media: vicodec: Add support for resolution change event.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1662bfbd200000
start commit: 3b15f68e media: vicodec: Add support for resolution change..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=1562bfbd200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1162bfbd200000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2b2e9c0bc43c14d
dashboard link: https://syzkaller.appspot.com/bug?extid=f9966a25169b6d66d61f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1342c7a0c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a241c4c00000
Reported-by: syzbot+f9966a25169b6d66d61f@syzkaller.appspotmail.com
Fixes: 3b15f68e19c2 ("media: vicodec: Add support for resolution change
event.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-03-21 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 19:51 WARNING in vb2_core_reqbufs syzbot
2019-01-29 7:58 ` syzbot
2019-03-21 15:55 ` 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=000000000000b87c6405849cc2d6@google.com \
--to=syzbot+f9966a25169b6d66d61f@syzkaller.appspotmail.com \
--cc=dafna3@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.com \
--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