From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+4455ca3b3291de891abc@syzkaller.appspotmail.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI <dri-devel@lists.freedesktop.org>,
ghalat@redhat.com, Gleb Natapov <gleb@kernel.org>,
gwshan@linux.vnet.ibm.com, "H. Peter Anvin" <hpa@zytor.com>,
James Morris <jmorris@namei.org>,
kasan-dev <kasan-dev@googlegroups.com>,
KVM list <kvm@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Russell Currey <ruscur@russell.cc>,
Sam Ravnborg <sam@ravnborg.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
stewart@linux.vnet.ibm.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: KASAN: slab-out-of-bounds Read in fbcon_get_font
Date: Thu, 5 Dec 2019 12:29:20 +0100 [thread overview]
Message-ID: <bf93410c-7e59-a679-c00d-5333a9879128@redhat.com> (raw)
In-Reply-To: <CACT4Y+YopHoCFDRHCE6brnWfHb5YUsTJS1Mc+58GgO8CDEcgHQ@mail.gmail.com>
On 05/12/19 12:27, Dmitry Vyukov wrote:
> Oh, you mean the final bisection crash. Indeed it contains a kvm frame
> and it turns out to be a bug in syzkaller code that indeed
> misattributed it to kvm instead of netfilter.
> Should be fixed now, you may read the commit message for details:
> https://github.com/google/syzkaller/commit/4fb74474cf0af2126be3a8989d770c3947ae9478
>
> Overall this "making sense out of kernel output" task is the ultimate
> insanity, you may skim through this file to get a taste of amount of
> hardcoding and special corner cases that need to be handled:
> https://github.com/google/syzkaller/blob/master/pkg/report/linux.go
> And this is never done, such "exception from exception corner case"
> things pop up every week. There is always something to shuffle and
> tune. It only keeps functioning due to 500+ test cases for all
> possible insane kernel outputs:
> https://github.com/google/syzkaller/tree/master/pkg/report/testdata/linux/report
> https://github.com/google/syzkaller/tree/master/pkg/report/testdata/linux/guilty
>
> So thanks for persisting and questioning! We are getting better with
> each new test.
Thanks to you! I "complain" because I know you're so responsive. :)
Paolo
next prev parent reply other threads:[~2019-12-05 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000002cfc3a0598d42b70@google.com>
2019-12-04 21:41 ` KASAN: slab-out-of-bounds Read in fbcon_get_font syzbot
2019-12-05 1:59 ` Tetsuo Handa
2019-12-05 10:13 ` Paolo Bonzini
2019-12-05 10:16 ` Dmitry Vyukov
2019-12-05 10:22 ` Paolo Bonzini
2019-12-05 10:31 ` Dmitry Vyukov
2019-12-05 10:53 ` Paolo Bonzini
2019-12-05 11:27 ` Dmitry Vyukov
2019-12-05 11:29 ` Paolo Bonzini [this message]
2019-12-05 10:41 ` Tetsuo Handa
2019-12-05 11:35 ` Dmitry Vyukov
2019-12-05 11:36 ` Dmitry Vyukov
2019-12-05 10:30 ` Tetsuo Handa
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=bf93410c-7e59-a679-c00d-5333a9879128@redhat.com \
--to=pbonzini@redhat.com \
--cc=aryabinin@virtuozzo.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=ghalat@redhat.com \
--cc=gleb@kernel.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=kasan-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=ruscur@russell.cc \
--cc=sam@ravnborg.org \
--cc=serge@hallyn.com \
--cc=stewart@linux.vnet.ibm.com \
--cc=syzbot+4455ca3b3291de891abc@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).