[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+YAyK02ORyzS79ub+XOK6x5LV8_2k4aztwzjP=0dm--RQ@mail.gmail.com>
Date: Mon, 10 Jul 2023 09:43:36 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: "Lameter, Christopher" <cl@...amperecomputing.com>
Cc: David Rientjes <rientjes@...gle.com>,
syzbot <syzbot+cf0693aee9ea61dda749@...kaller.appspotmail.com>,
42.hyeyoo@...il.com, Andrew Morton <akpm@...ux-foundation.org>,
iamjoonsoo.kim@....com, keescook@...omium.org,
linux-fsdevel@...r.kernel.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
penberg@...nel.org, reiserfs-devel@...r.kernel.org,
roman.gushchin@...ux.dev, syzkaller-bugs@...glegroups.com,
Vlastimil Babka <vbabka@...e.cz>, Jan Kara <jack@...e.cz>
Subject: Re: [syzbot] [mm?] [reiserfs?] kernel panic: stack is corrupted in ___slab_alloc
On Thu, 6 Jul 2023 at 20:33, Lameter, Christopher
<cl@...amperecomputing.com> wrote:
>
> On Mon, 3 Jul 2023, Dmitry Vyukov wrote:
>
> >> This is happening during while mounting reiserfs, so I'm inclined to think
> >> it's more of a reisterfs issue than a slab allocator issue :/
>
> Have you tried to run with the "slub_debug" kernel option to figure out
> what got corrupted?
Can slub_debug detect anything that KASAN can't?
I would assume KASAN can detect more bugs (e.g. stack/globals) and
report way better. And it was already enabled in the config.
Powered by blists - more mailing lists