linux-kernel - Re: KASAN / KUNIT: testing ran on qemu-arm and list of failures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdb8ynRrXZ0O4cxoGSn2zQ1rr7zkDiTz78Pm+GPc30p_Nw@mail.gmail.com>
Date:   Tue, 8 Nov 2022 14:51:04 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     open list <linux-kernel@...r.kernel.org>,
        linux-stable <stable@...r.kernel.org>,
        Kees Cook <keescook@...omium.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        David Gow <davidgow@...gle.com>,
        Gwan-gyeong Mun <gwan-gyeong.mun@...el.com>,
        Vitor Massaru Iha <vitor@...saru.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: KASAN / KUNIT: testing ran on qemu-arm and list of failures

On Wed, Nov 2, 2022 at 3:15 PM Naresh Kamboju <naresh.kamboju@...aro.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@...aro.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