Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <010001647fcab0b9-1154d4da-94f8-404e-8898-b8acdf366592-000000@email.amazonses.com>
References: <000000000000afa87d05708af289@google.com> <010001647fcab0b9-1154d4da-94f8-404e-8898-b8acdf366592-000000@email.amazonses.com>
From:   Dmitry Vyukov <dvyukov@google.com>
Date:   Mon, 9 Jul 2018 18:16:02 +0200
Message-ID: <CACT4Y+ZiVLw4pEt_GXV0DDo95eER5LuwXRo_fjFLwP8fUXzcrQ@mail.gmail.com>
Subject: Re: kernel BUG at mm/slab.c:LINE! (2)
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>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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