From: Qian Cai <cai@lca.pw>
To: syzbot <syzbot+95bccd805a4aa06a4b0d@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: linux-next boot error: WARNING in kmem_cache_free
Date: Mon, 22 Jun 2020 02:29:35 -0400 [thread overview]
Message-ID: <4A35E92B-9DEF-4833-81DD-0C6FA50EB174@lca.pw> (raw)
In-Reply-To: <000000000000617f9d05a8a5a2c4@google.com>
> On Jun 22, 2020, at 1:37 AM, syzbot <syzbot+95bccd805a4aa06a4b0d@syzkaller.appspotmail.com> wrote:
>
> WARNING: CPU: 0 PID: 0 at mm/slab.h:232 kmem_cache_free+0x0/0x200 mm/slab.c:2262
Is there any particular reason to use CONFIG_SLAB rather than CONFIG_SLUB?
You are really asking for trouble to test something that almost nobody is exercising that code path very well nowadays.
Anyway, there is a patchset in -mm that might well introduce this regression that we could go to confirm it, but I kind of don’t want to spend too much time on SLAB that suppose to be obsolete eventually.
next prev parent reply other threads:[~2020-06-22 6:29 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 [this message]
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
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=4A35E92B-9DEF-4833-81DD-0C6FA50EB174@lca.pw \
--to=cai@lca.pw \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+95bccd805a4aa06a4b0d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).