linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Eric Biggers <ebiggers@kernel.org>
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
Subject: Re: linux-next boot error: WARNING in kmem_cache_free
Date: Sat, 27 Jun 2020 20:49:30 -0400	[thread overview]
Message-ID: <CE087189-8054-4D2F-AAB1-2D75CF1BFC15@lca.pw> (raw)
In-Reply-To: <20200627231013.GM7065@sol.localdomain>



> On Jun 27, 2020, at 7:10 PM, Eric Biggers <ebiggers@kernel.org> wrote:
> 
> 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:
> 
> #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.

      reply	other threads:[~2020-06-28  0:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  5:37 linux-next boot error: WARNING in kmem_cache_free syzbot
2020-06-22  6:29 ` Qian Cai
2020-06-22  6:42   ` Dmitry Vyukov
2020-06-22  7:28     ` Qian Cai
2020-06-27 23:10       ` Eric Biggers
2020-06-28  0:49         ` Qian Cai [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=CE087189-8054-4D2F-AAB1-2D75CF1BFC15@lca.pw \
    --to=cai@lca.pw \
    --cc=dvyukov@google.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=syzbot+95bccd805a4aa06a4b0d@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).