From: syzbot <syzbot+4180ff9ca6810b06c1e9@syzkaller.appspotmail.com>
To: hans.verkuil@cisco.com, helen.koike@collabora.com,
hverkuil@xs4all.nl, kyungmin.park@samsung.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
m.szyprowski@samsung.com, mchehab@kernel.org,
mchehab@s-opensource.com, mhjungk@gmail.com, pawel@osciak.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in __vb2_perform_fileio
Date: Tue, 09 Apr 2019 14:18:00 -0700 [thread overview]
Message-ID: <000000000000da9f1505861f7cfb@google.com> (raw)
In-Reply-To: <00000000000091818d05795d0f2f@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=15fbb7a7200000
start commit: 38e7571c Merge tag 'io_uring-2019-03-06' of git://git.kern..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17fbb7a7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13fbb7a7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c9125b2c20e6dd4
dashboard link: https://syzkaller.appspot.com/bug?extid=4180ff9ca6810b06c1e9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101eda5f200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c465db200000
Reported-by: syzbot+4180ff9ca6810b06c1e9@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-09 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 12:18 KASAN: use-after-free Read in __vb2_perform_fileio syzbot
2019-04-09 21:18 ` 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=000000000000da9f1505861f7cfb@google.com \
--to=syzbot+4180ff9ca6810b06c1e9@syzkaller.appspotmail.com \
--cc=hans.verkuil@cisco.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil@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@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=mhjungk@gmail.com \
--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 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.