From: Alexander Potapenko <glider@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
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: Fri, 13 Jan 2023 15:57:28 +0100 [thread overview]
Message-ID: <CAG_fn=WE4_DVyxjjq6YW-_bZm6JXE3smy_qw9VTZh9wgV+Gj4g@mail.gmail.com> (raw)
In-Reply-To: <Y8Fq5m0CLfcFLCOY@zn.tnic>
On Fri, Jan 13, 2023 at 3:30 PM Borislav Petkov <bp@alien8.de> wrote:
>
> Hi,
>
> Lemme CC the stackdepot.c commit signers re the below splat.
>
> Lemme know if you need more info.
The kernel commit and config would help.
Is this somehow related to SLUB_TINY? Perhaps stack depot is just
trying to allocate way more memory than allowed?
(I see that Memory: below shows a lot of free pages, but am not sure
how it works with SLUB_TINY).
> Thx.
>
> ...
> [ 0.000000] software IO TLB: area num 4.
> [ 0.000000] Memory: 15612528K/16165300K available (12288K kernel code, 116072K rwdata, 5024K rodata, 2412K init, 3822
next prev parent reply other threads:[~2023-01-13 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:29 Borislav Petkov
2023-01-13 14:57 ` Alexander Potapenko [this message]
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
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='CAG_fn=WE4_DVyxjjq6YW-_bZm6JXE3smy_qw9VTZh9wgV+Gj4g@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox