From: syzbot <syzbot+13013adc4a234406c29e@syzkaller.appspotmail.com>
To: b.zolnierkie@samsung.com, daniel.thompson@linaro.org,
daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
ghalat@redhat.com, gregkh@linuxfoundation.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, sam@ravnborg.org,
syzkaller-bugs@googlegroups.com
Subject: Re: divide error in fbcon_switch
Date: Mon, 27 Jul 2020 16:45:08 +0000 [thread overview]
Message-ID: <0000000000009c18f005ab6f0bc0@google.com> (raw)
In-Reply-To: <00000000000072cb4c0598d25a69@google.com>
syzbot suspects this issue was fixed by commit:
commit ce684552a266cb1c7cc2f7e623f38567adec6653
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Sun Jul 12 11:10:12 2020 +0000
vt: Reject zero-sized screen buffer size.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x155549c4900000
start commit: 76bb8b05 Merge tag 'kbuild-v5.5' of git://git.kernel.org/p..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?xÝ226651cb0f364b
dashboard link: https://syzkaller.appspot.com/bug?extid\x13013adc4a234406c29e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x17d69aeae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x13fdcc2ae00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: vt: Reject zero-sized screen buffer size.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-07-27 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 20:15 divide error in fbcon_switch syzbot
2020-07-27 16:45 ` 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=0000000000009c18f005ab6f0bc0@google.com \
--to=syzbot+13013adc4a234406c29e@syzkaller.appspotmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sam@ravnborg.org \
--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).