From: syzbot <syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com>
To: bwinther@cisco.com, hans.verkuil@cisco.com,
helen.koike@collabora.com, hverkuil-cisco@xs4all.nl,
hverkuil@xs4all.nl, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, mchehab@s-opensource.com,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel paging request in tpg_fill_plane_buffer
Date: Tue, 09 Apr 2019 21:44:00 -0700 [thread overview]
Message-ID: <000000000000e50a29058625b741@google.com> (raw)
In-Reply-To: <0000000000005b7c64057ba003fb@google.com>
syzbot has bisected this bug to:
commit f2fe89061d79706eca5c47e4efdc09bbc171e74a
Author: Helen Koike <helen.koike@collabora.com>
Date: Fri Apr 7 17:55:19 2017 +0000
[media] vimc: Virtual Media Controller core, capture and sensor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b9542d200000
start commit: 6a1d2932 Add linux-next specific files for 20181224
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16b9542d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12b9542d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9369d117d073843
dashboard link: https://syzkaller.appspot.com/bug?extid=aa8212f63ea8ffaf3bfa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d0363b400000
Reported-by: syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com
Fixes: f2fe89061d79 ("[media] vimc: Virtual Media Controller core, capture
and sensor")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-10 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 7:01 BUG: unable to handle kernel paging request in tpg_fill_plane_buffer syzbot
2018-12-25 12:37 ` syzbot
2019-04-10 4:44 ` 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=000000000000e50a29058625b741@google.com \
--to=syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com \
--cc=bwinther@cisco.com \
--cc=hans.verkuil@cisco.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.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 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.