All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Andrew Morton <akpm@linux-foundation.org>
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 22:11:31 +0100	[thread overview]
Message-ID: <Y9bhAyu9IJ9yBdN2@zn.tnic> (raw)
In-Reply-To: <20230129125014.fcd459335c9b8eae71067c1a@linux-foundation.org>

On Sun, Jan 29, 2023 at 12:50:14PM -0800, Andrew Morton wrote:
> OK, thanks, I didn't realize this issue was so serious.

Yeah, I wouldn't call it serious - as a precondition, you need KMEMLEAK enabled
which probably shouldn't be run in production. For some reason it was enabled in
that test box's config - that's how I even saw this in the first place...

-- 
Regards/Gruss,
    Boris.

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

      reply	other threads:[~2023-01-29 21:11 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
2023-01-29 21:11           ` Borislav Petkov [this message]

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=Y9bhAyu9IJ9yBdN2@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 \
    --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 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.