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: <CA+G9fYv5-og6kr8PgGCg-wYUK3PGCQmvbY1YYews5-C8XwxSww@mail.gmail.com>
In-Reply-To: <CA+G9fYv5-og6kr8PgGCg-wYUK3PGCQmvbY1YYews5-C8XwxSww@mail.gmail.com>
From:   Linus Walleij <linus.walleij@linaro.org>
Date:   Tue, 8 Nov 2022 14:51:04 +0100
Message-ID: <CACRpkdb8ynRrXZ0O4cxoGSn2zQ1rr7zkDiTz78Pm+GPc30p_Nw@mail.gmail.com>
Subject: Re: KASAN / KUNIT: testing ran on qemu-arm and list of failures
To:     Naresh Kamboju <naresh.kamboju@linaro.org>
Cc:     open list <linux-kernel@vger.kernel.org>,
        linux-stable <stable@vger.kernel.org>,
        Kees Cook <keescook@chromium.org>,
        Vlastimil Babka <vbabka@suse.cz>,
        David Gow <davidgow@google.com>,
        Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>,
        Vitor Massaru Iha <vitor@massaru.org>,
        Arnd Bergmann <arnd@arndb.de>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Nov 2, 2022 at 3:15 PM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:

> This is a report to get a quick update on kasan on qemu-arm.
>
> The KASAN / KUNIT testing ran on qemu-arm and the following test cases failed
> and the kernel crashed.
>
> Following tests failed,
>     kasan_strings - FAILED
>     vmalloc_oob - FAILED
>     kasan_memchr - FAILED
>     kasan - FAILED
>     kasan_bitops_generic - FAILED
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Which isn't very strange since:

> [  429.920201] Insufficient stack space to handle exception!

the system ran out of stack. With VMAP stack and IRQSTACKS
there is really not much more memory we can provide.

When I discussed this with syzbot it seemed they were using some
really big userspace program written in Go that just used up all
the virtual memory :P

I don't know the nature of this test though. Using a lot of memory??

Yours,
Linus Walleij