[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y8ZMHi4IGP+v7biC@xsang-OptiPlex-9020>
Date: Tue, 17 Jan 2023 15:19:58 +0800
From: Oliver Sang <oliver.sang@...el.com>
To: Vlastimil Babka <vbabka@...e.cz>
CC: Hyeonggon Yoo <42.hyeyoo@...il.com>, <oe-lkp@...ts.linux.dev>,
<lkp@...el.com>, Mike Rapoport <rppt@...ux.ibm.com>,
Christoph Lameter <cl@...ux.com>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
Matthew Wilcox <willy@...radead.org>
Subject: Re: [linus:master] [mm, slub] 0af8489b02:
kernel_BUG_at_include/linux/mm.h
Hi, Vlastimil,
On Thu, Jan 12, 2023 at 08:56:59AM +0100, Vlastimil Babka wrote:
>
> Actually no, by "obscure" means with CONFIG_SLUB_DEBUG it wouldn't happen
> anymore. But this is the opposite, it seems to happen a lot. I would have
> preferred that slub debugging catches some slab misuse, but this seems
> useful too. With such fail rates you can perhaps try ealier kernels than 6.0
> and eventually find the truly clean and first bad release and bisect?
Thanks a lot for guidance!
yeah, we reached back to until v5.14-rc1 which still has similar issue,
and v5.13 is clean. new bisection was triggered then we got '7118fc2906'
this was already reported as
"[linus:master] [hugetlb] 7118fc2906: kernel_BUG_at_lib/list_debug.c"
at https://lore.kernel.org/all/202301170941.49728982-oliver.sang@intel.com/
and I add you, Hyeonggon, Feng and Fengwei there.
hope that would be helpful.
Powered by blists - more mailing lists