From: syzbot <syzbot+52e5bf0ebfa66092937a@syzkaller.appspotmail.com>
To: hansverk@cisco.com, hverkuil@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, tfiga@chromium.org
Subject: Re: general protection fault in vb2_mmap
Date: Thu, 07 Nov 2019 05:42:07 -0800 [thread overview]
Message-ID: <000000000000d5dacd0596c1d41e@google.com> (raw)
In-Reply-To: <00000000000014008b057a598671@google.com>
syzbot suspects this bug was fixed by commit:
commit cd26d1c4d1bc947b56ae404998ae2276df7b39b7
Author: Hans Verkuil <hverkuil@xs4all.nl>
Date: Tue Nov 13 14:06:46 2018 +0000
media: vb2: vb2_mmap: move lock up
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101a70e2600000
start commit: e12e00e3 Merge tag 'kbuild-fixes-v4.20' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8f215f21f041a0d7
dashboard link: https://syzkaller.appspot.com/bug?extid=52e5bf0ebfa66092937a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c61b0b400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=109d545d400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: media: vb2: vb2_mmap: move lock up
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: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 1:30 general protection fault in vb2_mmap syzbot
2018-11-11 23:42 ` syzbot
2019-03-21 17:39 ` syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-11 14:02 ` 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=000000000000d5dacd0596c1d41e@google.com \
--to=syzbot+52e5bf0ebfa66092937a@syzkaller.appspotmail.com \
--cc=hansverk@cisco.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+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tfiga@chromium.org \
/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).