Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: linux-next boot error: WARNING in kmem_cache_free
Date:   Sat, 27 Jun 2020 20:49:30 -0400
Message-Id: <CE087189-8054-4D2F-AAB1-2D75CF1BFC15@lca.pw>
References: <20200627231013.GM7065@sol.localdomain>
Cc:     Dmitry Vyukov <dvyukov@google.com>,
        syzbot <syzbot+95bccd805a4aa06a4b0d@syzkaller.appspotmail.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
        linux-mm@kvack.org
In-Reply-To: <20200627231013.GM7065@sol.localdomain>
To:     Eric Biggers <ebiggers@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Jun 27, 2020, at 7:10 PM, Eric Biggers <ebiggers@kernel.org> wrote:
>=20
> This bug also got reported 2 days later by the kernel test robot
> (lore.kernel.org/lkml/20200623090213.GW5535@shao2-debian/).
> Then it was fixed by commit 437edcaafbe3, so telling syzbot:
>=20
> #syz fix: mm, slab/slub: improve error reporting and overhead of cache_fro=
m_obj()-fix
>=20
> If CONFIG_SLAB is no longer useful and supported then it needs to be remov=
ed
> from the kernel.  Otherwise, it needs to be tested just like all other opt=
ions.

It is awesome that kernel test robot was able to bisect it which is especial=
ly useful for testing legacy options like SLAB.=