[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61032955-4200-662b-ace8-bad47d337cdc@os.amperecomputing.com>
Date: Thu, 6 Jul 2023 11:33:00 -0700 (PDT)
From: "Lameter, Christopher" <cl@...amperecomputing.com>
To: Dmitry Vyukov <dvyukov@...gle.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 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?
Powered by blists - more mailing lists