[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f2f54eccdbda3bd09eee8bf50264133faf84b80f.camel@gmx.de>
Date: Thu, 15 Apr 2021 20:13:58 +0200
From: Mike Galbraith <efault@....de>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: "Zhang, Qiang" <Qiang.Zhang@...driver.com>,
Andrew Halaney <ahalaney@...hat.com>,
"andreyknvl@...il.com" <andreyknvl@...il.com>,
"ryabinin.a.a@...il.com" <ryabinin.a.a@...il.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kasan-dev@...glegroups.com" <kasan-dev@...glegroups.com>
Subject: Re: Question on KASAN calltrace record in RT
On Wed, 2021-04-14 at 07:26 +0200, Dmitry Vyukov wrote:
>
> > [ 15.428008] ==================================================================
> > [ 15.428011] BUG: KASAN: vmalloc-out-of-bounds in crash_setup_memmap_entries+0x17e/0x3a0
>
> This looks like a genuine kernel bug on first glance. I think it needs
> to be fixed rather than ignored.
I posted a fix, so KASAN earns another notch in its pistol grips.
-Mike
Powered by blists - more mailing lists