[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230117161818.2dba77f3ee9b8709947b58f2@linux-foundation.org>
Date: Tue, 17 Jan 2023 16:18:18 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "zhaoyang.huang" <zhaoyang.huang@...soc.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Vlastimil Babka <vbabka@...e.cz>,
"Nathan Chancellor" <nathan@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Zhaoyang Huang <huangzhaoyang@...il.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <ke.wang@...soc.com>,
Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
Subject: Re: [PATCHv2] mm: use stack_depot_early_init for kmemleak
On Tue, 17 Jan 2023 16:11:52 +0800 "zhaoyang.huang" <zhaoyang.huang@...soc.com> wrote:
> Mirsad report bellow error which caused by stack_depot_init failed in kvcalloc.
> Solve this by having stackdepot use stack_depot_early_init. Extra Kconfig also
> done by moving kmemleak stuff to mm/Kconfig.debug.
Are we able to identify which commit caused this regression?
Thanks.
Powered by blists - more mailing lists