All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
	Vlastimil Babka <vbabka@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	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>
Subject: Re: Failure during Stack Depot allocating hash table of 1048576 entries with kvcalloc
Date: Sat, 28 Jan 2023 15:26:00 +0100	[thread overview]
Message-ID: <Y9UweHxSfPiAqgZx@zn.tnic> (raw)
In-Reply-To: <d4871e70-c7c9-e638-d7c0-304ec8aea77b@leemhuis.info>

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>

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2023-01-28 14:26 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 [this message]
2023-01-29 20:50         ` Andrew Morton
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=Y9UweHxSfPiAqgZx@zn.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.