From: syzbot <syzbot+f11cda116c57db68c227@syzkaller.appspotmail.com>
To: b.zolnierkie@samsung.com, daniel.vetter@ffwll.ch,
daniel.vetter@intel.com, dri-devel@lists.freedesktop.org,
hdanton@sina.com, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mojha@codeaurora.org, sam@ravnborg.org,
shile.zhang@linux.alibaba.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in fb_mode_is_equal
Date: Wed, 25 Dec 2019 15:26:00 +0000 [thread overview]
Message-ID: <000000000000c6e365059a88e032@google.com> (raw)
In-Reply-To: <0000000000001b2f4605991a4cc0@google.com>
In-Reply-To: <0000000000001b2f4605991a4cc0@google.com>
syzbot has bisected this bug to:
commit 13ff178ccd6d3b8074c542a911300b79c4eec255
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Tue May 28 09:02:53 2019 +0000
fbcon: Call fbcon_mode_deleted/new_modelist directly
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x1737c63ee00000
start commit: 46cf053e Linux 5.5-rc3
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x\x14b7c63ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x\x10b7c63ee00000
kernel config: https://syzkaller.appspot.com/x/.config?xí9d672709340e35
dashboard link: https://syzkaller.appspot.com/bug?extidñ1cda116c57db68c227
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x12bf72c6e00000
Reported-by: syzbot+f11cda116c57db68c227@syzkaller.appspotmail.com
Fixes: 13ff178ccd6d ("fbcon: Call fbcon_mode_deleted/new_modelist directly")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-25 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 10:05 KASAN: use-after-free Read in fb_mode_is_equal syzbot
2019-12-25 8:17 ` syzbot
2019-12-25 15: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=000000000000c6e365059a88e032@google.com \
--to=syzbot+f11cda116c57db68c227@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=hdanton@sina.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mojha@codeaurora.org \
--cc=sam@ravnborg.org \
--cc=shile.zhang@linux.alibaba.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 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).