Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <Y8Fq5m0CLfcFLCOY@zn.tnic>
In-Reply-To: <Y8Fq5m0CLfcFLCOY@zn.tnic>
From:   Alexander Potapenko <glider@google.com>
Date:   Fri, 13 Jan 2023 15:57:28 +0100
Message-ID: <CAG_fn=WE4_DVyxjjq6YW-_bZm6JXE3smy_qw9VTZh9wgV+Gj4g@mail.gmail.com>
Subject: Re: Failure during Stack Depot allocating hash table of 1048576
 entries with kvcalloc
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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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