Date:   Sun, 29 Jan 2023 12:50:14 -0800
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Borislav Petkov <bp@alien8.de>
Cc:     Linux regressions mailing list <regressions@lists.linux.dev>,
        Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
        Vlastimil Babka <vbabka@suse.cz>,
        Alexander Potapenko <glider@google.com>,
        Marco Elver <elver@google.com>,
        Dmitry Vyukov <dvyukov@google.com>,
        linux-mm <linux-mm@kvack.org>,
        lkml <linux-kernel@vger.kernel.org>,
        Zhaoyang Huang <zhaoyang.huang@unisoc.com>
Subject: Re: Failure during Stack Depot allocating hash table of 1048576
 entries with kvcalloc
Message-Id: <20230129125014.fcd459335c9b8eae71067c1a@linux-foundation.org>
In-Reply-To: <Y9UweHxSfPiAqgZx@zn.tnic>
References: <Y8Fq5m0CLfcFLCOY@zn.tnic>
        <07e42002-e78d-7947-19a7-0dd035466f50@alu.unizg.hr>
        <Y9UBFNwBeuePPsk3@zn.tnic>
        <d4871e70-c7c9-e638-d7c0-304ec8aea77b@leemhuis.info>
        <Y9UweHxSfPiAqgZx@zn.tnic>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Sat, 28 Jan 2023 15:26:00 +0100 Borislav Petkov <bp@alien8.de> wrote:

> On Sat, Jan 28, 2023 at 02:55:58PM +0100, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> > On 28.01.23 12:03, Borislav Petkov wrote:
> > > On Sat, Jan 28, 2023 at 03:41:50AM +0100, Mirsad Goran Todorovac wrote:
> > >> This appears to be a duplicate of the report:
> > >> https://lore.kernel.org/linux-mm/2c677d85-820c-d41a-fc98-7d3974b49e42@alu.unizg.hr/raw
> > > 
> > > Yah, looks like
> > > 
> > > 56a61617dd22 ("mm: use stack_depot for recording kmemleak's backtrace")
> > > 
> > > needs to be reverted.
> > 
> > Unless I'm missing something (which might easily be the case) there is a
> > patch for that issue in -mm already:
> > 
> > https://lore.kernel.org/all/20230119224022.80752C433F0@smtp.kernel.org/
> > 
> > Or where two different issues discussed in the thread Mirsad mentioned
> > above?
> 
> Probably the same issue. This one fixes the issue on my machine - thanks!
> 
> Tested-by: Borislav Petkov (AMD) <bp@alien8.de>
> 

OK, thanks, I didn't realize this issue was so serious.

I reordered Zhaoyang Huang's series so that "mm: use
stack_depot_early_init for kmemleak" comes ahead of "mm: move
KMEMLEAK's Kconfig items from lib to mm" and I've staged "mm: use
stack_depot_early_init for kmemleak" in the mm-hotfixes branch for
upstream merging in this -rc cycle.