[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9UweHxSfPiAqgZx@zn.tnic>
Date: Sat, 28 Jan 2023 15:26:00 +0100
From: Borislav Petkov <bp@...en8.de>
To: Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexander Potapenko <glider@...gle.com>,
Marco Elver <elver@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
linux-mm <linux-mm@...ck.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: Failure during Stack Depot allocating hash table of 1048576
entries with kvcalloc
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@...en8.de>
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists