From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org,
syzbot <syzbot+b38b1ef6edf0c74a8d97@syzkaller.appspotmail.com>,
b.zolnierkie@samsung.com, daniel.vetter@ffwll.ch,
syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, george.kennedy@oracle.com,
natechancellor@gmail.com, jirislaby@kernel.org
Subject: Re: [PATCH] fbcon: Fix user font detection test at fbcon_resize().
Date: Wed, 16 Sep 2020 19:06:31 +0900 [thread overview]
Message-ID: <3233dcc2-31d5-42e7-3d9d-b36a65b660ea@i-love.sakura.ne.jp> (raw)
In-Reply-To: <20200916082624.GC509119@kroah.com>
On 2020/09/16 17:26, Greg KH wrote:
> On Wed, Sep 16, 2020 at 09:01:06AM +0900, Tetsuo Handa wrote:
>> Greg, will you pick up this patch?
>>
>> It seems that finding the real cause of [3] and actually fixing [3] will be difficult.
>> Since I can't reproduce [3] locally, I will have to try flood of "#syz test" requests
>> for debug printk() patches.
>
> I agree with Daniel here, can you retest these against Linus's latest
> tree please?
>
syzbot already reproduced these bugs using the latest commit. ;-)
You can find
ci-upstream-kasan-gce-root 2020/09/15 15:18 upstream fc4f28bb
record for "KASAN: global-out-of-bounds Read in bit_putcs" and
ci-upstream-kasan-gce-root 2020/09/16 09:54 upstream fc4f28bb
record for "KASAN: global-out-of-bounds Read in fbcon_resize".
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-09-16 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 5:35 KASAN: global-out-of-bounds Read in fbcon_resize syzbot
2020-09-10 22:57 ` [PATCH] fbcon: Fix user font detection test at fbcon_resize() Tetsuo Handa
2020-09-16 0:01 ` Tetsuo Handa
2020-09-16 7:44 ` Daniel Vetter
2020-09-16 8:26 ` Greg KH
2020-09-16 10:06 ` Tetsuo Handa [this message]
2020-09-16 12:35 ` Greg KH
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=3233dcc2-31d5-42e7-3d9d-b36a65b660ea@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--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=natechancellor@gmail.com \
--cc=syzbot+b38b1ef6edf0c74a8d97@syzkaller.appspotmail.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).