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
Date: Sun, 29 Jan 2023 12:50:14 -0800 [thread overview]
Message-ID: <20230129125014.fcd459335c9b8eae71067c1a@linux-foundation.org> (raw)
In-Reply-To: <Y9UweHxSfPiAqgZx@zn.tnic>
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.
next prev parent reply other threads:[~2023-01-29 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:29 Failure during Stack Depot allocating hash table of 1048576 entries with kvcalloc Borislav Petkov
2023-01-13 14:57 ` Alexander Potapenko
2023-01-13 16:10 ` Borislav Petkov
2023-01-27 23:16 ` Borislav Petkov
2023-01-28 2:41 ` Mirsad Goran Todorovac
2023-01-28 11:03 ` Borislav Petkov
2023-01-28 13:55 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-28 14:26 ` Borislav Petkov
2023-01-29 20:50 ` Andrew Morton [this message]
2023-01-29 21:11 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230129125014.fcd459335c9b8eae71067c1a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=regressions@lists.linux.dev \
--cc=vbabka@suse.cz \
--cc=zhaoyang.huang@unisoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).