linux-kernel - Re: [lkp-robot] [x86/kasan] def0e7b54d: Kernel_panic-not_syncing:memblock_virt_alloc_try_nid:Failed_to_allocate#by tes_align=#nid=#from=#max

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] [day] [month] [year] [list]

Date:   Sat, 27 Jan 2018 09:30:37 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     kernel test robot <xiaolong.ye@...el.com>
cc:     Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Alexander Potapenko <glider@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        "H. Peter Anvin" <hpa@...or.com>, tipbuild@...or.com, lkp@...org
Subject: Re: [lkp-robot] [x86/kasan] def0e7b54d:
 Kernel_panic-not_syncing:memblock_virt_alloc_try_nid:Failed_to_allocate#by
 tes_align=#nid=#from=#max_addr=

On Sat, 27 Jan 2018, kernel test robot wrote:

> Hi, Andrey
> 
> Is this panic log expected with your commit?

Yes it is. It says that there is not enough memroy to run with KASAN. If
you revert it the machine will die with a NULL pointer dereference at some
other place w/o telling you what the reason is.

> [    0.000000] Kernel panic - not syncing: memblock_virt_alloc_try_nid: Failed to allocate 4096 bytes align=0x1000 nid=0 from=0x1000000 max_addr=0x0

Thanks,

	tglx