From: syzbot <syzbot+b67aaae8d3a927f68d20@syzkaller.appspotmail.com>
To: b.zolnierkie@samsung.com, daniel.vetter@ffwll.ch,
daniel.vetter@intel.com, dri-devel@lists.freedesktop.org,
george.kennedy@oracle.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, melissa.srw@gmail.com,
natechancellor@gmail.com, sam@ravnborg.org,
syzkaller-bugs@googlegroups.com, tzimmermann@suse.de,
yepeilin.cs@gmail.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in fbcon_cursor
Date: Sun, 17 Jan 2021 03:29:05 -0800 [thread overview]
Message-ID: <000000000000c37b3a05b916e95a@google.com> (raw)
In-Reply-To: <00000000000091111005b435456e@google.com>
syzbot has bisected this issue to:
commit ea40d7857d5250e5400f38c69ef9e17321e9c4a2
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Fri Oct 9 23:21:56 2020 +0000
drm/vkms: fbdev emulation support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=148e2748d00000
start commit: b3a3cbde Add linux-next specific files for 20210115
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=168e2748d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=128e2748d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6ea08dae6aab586f
dashboard link: https://syzkaller.appspot.com/bug?extid=b67aaae8d3a927f68d20
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15cd8fe0d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17af5258d00000
Reported-by: syzbot+b67aaae8d3a927f68d20@syzkaller.appspotmail.com
Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-17 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:36 BUG: unable to handle kernel NULL pointer dereference in fbcon_cursor syzbot
2021-01-17 8:53 ` syzbot
2021-01-17 11:29 ` syzbot [this message]
2021-01-18 9:29 ` Daniel Vetter
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=000000000000c37b3a05b916e95a@google.com \
--to=syzbot+b67aaae8d3a927f68d20@syzkaller.appspotmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=george.kennedy@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=melissa.srw@gmail.com \
--cc=natechancellor@gmail.com \
--cc=sam@ravnborg.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzimmermann@suse.de \
--cc=yepeilin.cs@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 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).