From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+a4edd73d589b0b7efbeb@syzkaller.appspotmail.com>
Cc: b.zolnierkie@samsung.com, bugs-a21@moonlit-rail.com,
dri-devel@lists.freedesktop.org, javierm@redhat.com,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
maxime@cerno.tech, ngraniel@cocobongo.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in bitfill_aligned (2)
Date: Thu, 12 May 2022 15:21:14 +0200 [thread overview]
Message-ID: <CACT4Y+bi-h7PGWqM=JyjvaTHcyzkg9nndUTVCyV-rADPYgHspA@mail.gmail.com> (raw)
In-Reply-To: <00000000000035befb05d6b91185@google.com>
On Sat, 29 Jan 2022 at 15:07, syzbot
<syzbot+a4edd73d589b0b7efbeb@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 0499f419b76f94ede08304aad5851144813ac55c
> Author: Javier Martinez Canillas <javierm@redhat.com>
> Date: Mon Jan 10 09:56:25 2022 +0000
>
> video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1752f5c0700000
> start commit: 2a987e65025e Merge tag 'perf-tools-fixes-for-v5.16-2021-12..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=7d5e878e3399b6cc
> dashboard link: https://syzkaller.appspot.com/bug?extid=a4edd73d589b0b7efbeb
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16671badb00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122beabdb00000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
Based on commit subject looks legit:
#syz fix: video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
prev parent reply other threads:[~2022-05-12 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 20:47 BUG: unable to handle kernel paging request in bitfill_aligned (2) syzbot
2021-12-09 18:25 ` [syzbot] " syzbot
2022-01-29 14:07 ` syzbot
2022-05-12 13:21 ` Dmitry Vyukov [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='CACT4Y+bi-h7PGWqM=JyjvaTHcyzkg9nndUTVCyV-rADPYgHspA@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=b.zolnierkie@samsung.com \
--cc=bugs-a21@moonlit-rail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=ngraniel@cocobongo.net \
--cc=syzbot+a4edd73d589b0b7efbeb@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).