From: syzbot <syzbot+6a8d618862e1fc55313d@syzkaller.appspotmail.com>
To: daniel.vetter@ffwll.ch, ghalat@redhat.com,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, nico@fluxnic.net,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, sam@ravnborg.org,
syzkaller-bugs@googlegroups.com, textshell@uchuujin.de
Subject: Re: BUG: unable to handle kernel paging request in insert_char
Date: Mon, 27 Jul 2020 14:26:05 -0700 [thread overview]
Message-ID: <00000000000069c23105ab72f8f9@google.com> (raw)
In-Reply-To: <000000000000dbe36f05996858db@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=14357d8c900000
start commit: 510c9788 Merge tag 'Wimplicit-fallthrough-5.5-rc2' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
dashboard link: https://syzkaller.appspot.com/bug?extid=6a8d618862e1fc55313d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ed05dee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e569b6e00000
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 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 7:12 BUG: unable to handle kernel paging request in insert_char syzbot
2019-12-16 21:39 ` syzbot
2020-07-27 21: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=00000000000069c23105ab72f8f9@google.com \
--to=syzbot+6a8d618862e1fc55313d@syzkaller.appspotmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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.