From: syzbot <syzbot+c37a14770d51a085a520@syzkaller.appspotmail.com>
To: b.zolnierkie@samsung.com, daniel.thompson@linaro.org,
daniel.vetter@ffwll.ch, daniel.vetter@intel.com,
ghalat@redhat.com, gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
nico@fluxnic.net, okash.khawaja@gmail.com, oleksandr@redhat.com,
sam@ravnborg.org, syzkaller-bugs@googlegroups.com,
textshell@uchuujin.de
Subject: Re: KASAN: slab-out-of-bounds Read in vc_do_resize
Date: Sun, 26 Jan 2020 03:26:00 -0800 [thread overview]
Message-ID: <00000000000065b384059d094190@google.com> (raw)
In-Reply-To: <00000000000044bcb8059a0a577e@google.com>
syzbot has bisected this bug to:
commit 9e1467002630065ed86c65ea28bfc9194fff6f0e
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Tue May 28 09:02:59 2019 +0000
fbcon: replace FB_EVENT_MODE_CHANGE/_ALL with direct calls
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=135a779ee00000
start commit: d96d875e Merge tag 'fixes_for_v5.5-rc8' of git://git.kerne..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=10da779ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=175a779ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=83c00afca9cf5153
dashboard link: https://syzkaller.appspot.com/bug?extid=c37a14770d51a085a520
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1659a721e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16aa59c9e00000
Reported-by: syzbot+c37a14770d51a085a520@syzkaller.appspotmail.com
Fixes: 9e1467002630 ("fbcon: replace FB_EVENT_MODE_CHANGE/_ALL with direct calls")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-26 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 8:28 KASAN: slab-out-of-bounds Read in vc_do_resize syzbot
2020-01-22 2:46 ` syzbot
2020-01-22 15:51 ` syzbot
2020-01-26 11:26 ` 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=00000000000065b384059d094190@google.com \
--to=syzbot+c37a14770d51a085a520@syzkaller.appspotmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=nico@fluxnic.net \
--cc=okash.khawaja@gmail.com \
--cc=oleksandr@redhat.com \
--cc=sam@ravnborg.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=textshell@uchuujin.de \
/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.