From: Dmitry Vyukov <dvyukov@google.com>
To: Christopher Lameter <cl@linux.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev <netdev@vger.kernel.org>
Cc: syzbot <syzbot+885bda95271928dc24eb@syzkaller.appspotmail.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: kernel BUG at mm/slab.c:LINE! (2)
Date: Mon, 9 Jul 2018 18:16:02 +0200 [thread overview]
Message-ID: <CACT4Y+ZiVLw4pEt_GXV0DDo95eER5LuwXRo_fjFLwP8fUXzcrQ@mail.gmail.com> (raw)
In-Reply-To: <010001647fcab0b9-1154d4da-94f8-404e-8898-b8acdf366592-000000@email.amazonses.com>
On Mon, Jul 9, 2018 at 6:05 PM, Christopher Lameter <cl@linux.com> wrote:
> On Sun, 8 Jul 2018, syzbot wrote:
>
>> kernel BUG at mm/slab.c:4421!
>
> Classic location that indicates memory corruption. Can we rerun this with
> CONFIG_SLAB_DEBUG? Alternatively use SLUB debugging for better debugging
> without rebuilding.
This runs with KASAN which is way more powerful than slab/slub debug.
There two other recent crashes in bpf_test_finish which has more info:
https://syzkaller.appspot.com/bug?id=f831c88feddf5f4de09b846bbe53e5b8c06e5c02
https://syzkaller.appspot.com/bug?id=059cee5623ce519359e7440ba6d0d6af8b82694e
next prev parent reply other threads:[~2018-07-09 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 6:16 syzbot
2018-07-09 16:05 ` Christopher Lameter
2018-07-09 16:16 ` Dmitry Vyukov [this message]
2018-07-09 16:30 ` Daniel Borkmann
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=CACT4Y+ZiVLw4pEt_GXV0DDo95eER5LuwXRo_fjFLwP8fUXzcrQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=ast@kernel.org \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+885bda95271928dc24eb@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