[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230117173145.867a06c1585728da1e9b6a54@linux-foundation.org>
Date: Tue, 17 Jan 2023 17:31:45 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Zhaoyang Huang <huangzhaoyang@...il.com>
Cc: "zhaoyang.huang" <zhaoyang.huang@...soc.com>,
Catalin Marinas <catalin.marinas@....com>,
Vlastimil Babka <vbabka@...e.cz>,
Nathan Chancellor <nathan@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, 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 Wed, 18 Jan 2023 09:25:48 +0800 Zhaoyang Huang <huangzhaoyang@...il.com> wrote:
> On Wed, Jan 18, 2023 at 8:17 AM Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > 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.
> >
> > I don't understand - what was the reason for the Kconfig change?
> The items related to kmemleak are moved from lib/Kconfig.debug to
> mm/Kconfig.debug
Well yes, but why?
Is that related to this bug fix? If not then please let's have that
change in a separate patch.
Powered by blists - more mailing lists