[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGWkznEUykN88ucXDEBQNtR-uL=yr6Bh7nfQ1YL_QqBAvF2AQg@mail.gmail.com>
Date: Wed, 18 Jan 2023 09:30:56 +0800
From: Zhaoyang Huang <huangzhaoyang@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
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, Jan 18, 2023 at 8:18 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.
>
> Are we able to identify which commit caused this regression?
Actually, It could be deemed as a defect of 'mm: use stack_depot for
recording kmemleak's backtrace'(56a61617d).
>
> Thanks.
Powered by blists - more mailing lists