[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <CE087189-8054-4D2F-AAB1-2D75CF1BFC15@lca.pw>
Date: Sat, 27 Jun 2020 20:49:30 -0400
From: Qian Cai <cai@....pw>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Dmitry Vyukov <dvyukov@...gle.com>,
syzbot <syzbot+95bccd805a4aa06a4b0d@...kaller.appspotmail.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
linux-mm@...ck.org
Subject: Re: linux-next boot error: WARNING in kmem_cache_free
> On Jun 27, 2020, at 7:10 PM, Eric Biggers <ebiggers@...nel.org> wrote:
>
> This bug also got reported 2 days later by the kernel test robot
> (lore.kernel.org/lkml/20200623090213.GW5535@...o2-debian/).
> Then it was fixed by commit 437edcaafbe3, so telling syzbot:
>
> #syz fix: mm, slab/slub: improve error reporting and overhead of cache_from_obj()-fix
>
> If CONFIG_SLAB is no longer useful and supported then it needs to be removed
> from the kernel. Otherwise, it needs to be tested just like all other options.
It is awesome that kernel test robot was able to bisect it which is especially useful for testing legacy options like SLAB.
Powered by blists - more mailing lists