From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 24CD7C282F6 for ; Mon, 21 Jan 2019 09:31:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DD82920989 for ; Mon, 21 Jan 2019 09:30:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=c-s.fr header.i=@c-s.fr header.b="hIytj5Bo" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727862AbfAUJa6 (ORCPT ); Mon, 21 Jan 2019 04:30:58 -0500 Received: from pegase1.c-s.fr ([93.17.236.30]:59092 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726418AbfAUJa5 (ORCPT ); Mon, 21 Jan 2019 04:30:57 -0500 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 43jmWF1zRMz9v3wl; Mon, 21 Jan 2019 10:30:49 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=hIytj5Bo; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id leApUuGXDrxc; Mon, 21 Jan 2019 10:30:49 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 43jmWF0jPhz9v3wk; Mon, 21 Jan 2019 10:30:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1548063049; bh=UbgCdASS/NfnsXEzoq8G1ErQtI53lUSLqab2fWj7UAo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=hIytj5BoDVU2x1+2codn6GYRz8mWvvdsfj9OtfwoKjwojmb5OC+ECg1zDeuXUihGs LLK8zAaCAA/+fCTVZDXLyZjXOIiZgtDOw8iI90/+JyXeTj2YFGzxIwMPDYuSVQWy6W EqFMQfTEe3h/05prhaU8pvsT5Kz2BReX37G5cyU4= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 74C098B79C; Mon, 21 Jan 2019 10:30:55 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Gh0IDk4Yupl9; Mon, 21 Jan 2019 10:30:55 +0100 (CET) Received: from PO15451 (po15451.idsi0.si.c-s.fr [172.25.231.2]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 322708B799; Mon, 21 Jan 2019 10:30:55 +0100 (CET) Subject: Re: [PATCH v3 3/3] powerpc/32: Add KASAN support To: Dmitry Vyukov Cc: Andrey Ryabinin , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Nicholas Piggin , "Aneesh Kumar K.V" , Alexander Potapenko , LKML , linuxppc-dev@lists.ozlabs.org, kasan-dev , Linux-MM References: <935f9f83393affb5d55323b126468ecb90373b88.1547289808.git.christophe.leroy@c-s.fr> <8d433501-a5a7-8e3b-03f7-ccdd0f8622e1@c-s.fr> From: Christophe Leroy Message-ID: Date: Mon, 21 Jan 2019 10:30:55 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 21/01/2019 à 10:24, Dmitry Vyukov a écrit : > On Mon, Jan 21, 2019 at 9:37 AM Christophe Leroy > wrote: >> >> >> >> Le 21/01/2019 à 09:30, Dmitry Vyukov a écrit : >>> On Mon, Jan 21, 2019 at 8:17 AM Christophe Leroy >>> wrote: >>>> >>>> >>>> >>>> Le 15/01/2019 à 18:23, Andrey Ryabinin a écrit : >>>>> >>>>> >>>>> On 1/12/19 2:16 PM, Christophe Leroy wrote: >>>>> >>>>>> +KASAN_SANITIZE_early_32.o := n >>>>>> +KASAN_SANITIZE_cputable.o := n >>>>>> +KASAN_SANITIZE_prom_init.o := n >>>>>> + >>>>> >>>>> Usually it's also good idea to disable branch profiling - define DISABLE_BRANCH_PROFILING >>>>> either in top of these files or via Makefile. Branch profiling redefines if() statement and calls >>>>> instrumented ftrace_likely_update in every if(). >>>>> >>>>> >>>>> >>>>>> diff --git a/arch/powerpc/mm/kasan_init.c b/arch/powerpc/mm/kasan_init.c >>>>>> new file mode 100644 >>>>>> index 000000000000..3edc9c2d2f3e >>>>> >>>>>> +void __init kasan_init(void) >>>>>> +{ >>>>>> + struct memblock_region *reg; >>>>>> + >>>>>> + for_each_memblock(memory, reg) >>>>>> + kasan_init_region(reg); >>>>>> + >>>>>> + pr_info("KASAN init done\n"); >>>>> >>>>> Without "init_task.kasan_depth = 0;" kasan will not repot bugs. >>>>> >>>>> There is test_kasan module. Make sure that it produce reports. >>>>> >>>> >>>> Thanks for the review. >>>> >>>> Now I get the following very early in boot, what does that mean ? >>> >>> This looks like an instrumented memset call before kasan shadow is >>> mapped, or kasan shadow is not zeros. Does this happen before or after >>> mapping of kasan_early_shadow_page? >> >> This is after the mapping of kasan_early_shadow_page. >> >>> This version seems to miss what x86 code has to clear the early shadow: >>> >>> /* >>> * kasan_early_shadow_page has been used as early shadow memory, thus >>> * it may contain some garbage. Now we can clear and write protect it, >>> * since after the TLB flush no one should write to it. >>> */ >>> memset(kasan_early_shadow_page, 0, PAGE_SIZE); >> >> In the early part, kasan_early_shadow_page is mapped read-only so I >> assumed this reset of its content was unneccessary. >> >> I'll try with it. >> >> Christophe > > As far as I understand machine memory contains garbage after boot, and > that page needs to be all 0's so we need to explicitly memset it. That page is in BSS so it is zeroed before kasan_early_init(). Though as expected, that memset() doesn't fix the issue. Indeed the problem is in kasan_init() : memblock_phys_alloc() doesn't zeroize the allocated memory. I changed it to memblock_alloc() and now it works. Thanks for your help, Christophe > > >>>> [ 0.000000] KASAN init done >>>> [ 0.000000] >>>> ================================================================== >>>> [ 0.000000] BUG: KASAN: unknown-crash in memblock_alloc_try_nid+0xd8/0xf0 >>>> [ 0.000000] Write of size 68 at addr c7ff5a90 by task swapper/0 >>>> [ 0.000000] >>>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted >>>> 5.0.0-rc2-s3k-dev-00559-g88aa407c4bce #772 >>>> [ 0.000000] Call Trace: >>>> [ 0.000000] [c094ded0] [c016c7e4] >>>> print_address_description+0x1a0/0x2b8 (unreliable) >>>> [ 0.000000] [c094df00] [c016caa0] kasan_report+0xe4/0x168 >>>> [ 0.000000] [c094df40] [c016b464] memset+0x2c/0x4c >>>> [ 0.000000] [c094df60] [c08731f0] memblock_alloc_try_nid+0xd8/0xf0 >>>> [ 0.000000] [c094df90] [c0861f20] mmu_context_init+0x58/0xa0 >>>> [ 0.000000] [c094dfb0] [c085ca70] start_kernel+0x54/0x400 >>>> [ 0.000000] [c094dff0] [c0002258] start_here+0x44/0x9c >>>> [ 0.000000] >>>> [ 0.000000] >>>> [ 0.000000] Memory state around the buggy address: >>>> [ 0.000000] c7ff5980: e2 a1 87 81 bd d4 a5 b5 f8 8d 89 e7 72 bc 20 24 >>>> [ 0.000000] c7ff5a00: e7 b9 c1 c7 17 e9 b4 bd a4 d0 e7 a0 11 15 a5 b5 >>>> [ 0.000000] >c7ff5a80: b5 e1 83 a5 2d 65 31 3f f3 e5 a7 ef 34 b5 69 b5 >>>> [ 0.000000] ^ >>>> [ 0.000000] c7ff5b00: 21 a5 c1 c1 b4 bf 2d e5 e5 c3 f5 91 e3 b8 a1 34 >>>> [ 0.000000] c7ff5b80: ad ef 23 87 3d a6 ad b5 c3 c3 80 b7 ac b1 1f 37 >>>> [ 0.000000] >>>> ================================================================== >>>> [ 0.000000] Disabling lock debugging due to kernel taint >>>> [ 0.000000] MMU: Allocated 76 bytes of context maps for 16 contexts >>>> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 8176 >>>> [ 0.000000] Kernel command line: console=ttyCPM0,115200N8 >>>> ip=192.168.2.7:192.168.2.2::255.0.0.0:vgoip:eth0:off kgdboc=ttyCPM0 >>>> [ 0.000000] Dentry cache hash table entries: 16384 (order: 2, 65536 >>>> bytes) >>>> [ 0.000000] Inode-cache hash table entries: 8192 (order: 1, 32768 bytes) >>>> [ 0.000000] Memory: 99904K/131072K available (7376K kernel code, 528K >>>> rwdata, 1168K rodata, 576K init, 4623K bss, 31168K reserved, 0K >>>> cma-reserved) >>>> [ 0.000000] Kernel virtual memory layout: >>>> [ 0.000000] * 0xffefc000..0xffffc000 : fixmap >>>> [ 0.000000] * 0xf7c00000..0xffc00000 : kasan shadow mem >>>> [ 0.000000] * 0xf7a00000..0xf7c00000 : consistent mem >>>> [ 0.000000] * 0xf7a00000..0xf7a00000 : early ioremap >>>> [ 0.000000] * 0xc9000000..0xf7a00000 : vmalloc & ioremap >>>> >>>> >>>> Christophe From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BD670C282DB for ; Mon, 21 Jan 2019 09:32:37 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3A3F3214DA for ; Mon, 21 Jan 2019 09:32:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=c-s.fr header.i=@c-s.fr header.b="hIytj5Bo" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3A3F3214DA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=c-s.fr Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 43jmYH20vjzDqXT for ; Mon, 21 Jan 2019 20:32:35 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=c-s.fr (client-ip=93.17.236.30; helo=pegase1.c-s.fr; envelope-from=christophe.leroy@c-s.fr; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=c-s.fr Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=c-s.fr header.i=@c-s.fr header.b="hIytj5Bo"; dkim-atps=neutral Received: from pegase1.c-s.fr (pegase1.c-s.fr [93.17.236.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43jmWS5WxCzDqTX for ; Mon, 21 Jan 2019 20:31:00 +1100 (AEDT) Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 43jmWF1zRMz9v3wl; Mon, 21 Jan 2019 10:30:49 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=hIytj5Bo; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id leApUuGXDrxc; Mon, 21 Jan 2019 10:30:49 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 43jmWF0jPhz9v3wk; Mon, 21 Jan 2019 10:30:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1548063049; bh=UbgCdASS/NfnsXEzoq8G1ErQtI53lUSLqab2fWj7UAo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=hIytj5BoDVU2x1+2codn6GYRz8mWvvdsfj9OtfwoKjwojmb5OC+ECg1zDeuXUihGs LLK8zAaCAA/+fCTVZDXLyZjXOIiZgtDOw8iI90/+JyXeTj2YFGzxIwMPDYuSVQWy6W EqFMQfTEe3h/05prhaU8pvsT5Kz2BReX37G5cyU4= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 74C098B79C; Mon, 21 Jan 2019 10:30:55 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Gh0IDk4Yupl9; Mon, 21 Jan 2019 10:30:55 +0100 (CET) Received: from PO15451 (po15451.idsi0.si.c-s.fr [172.25.231.2]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 322708B799; Mon, 21 Jan 2019 10:30:55 +0100 (CET) Subject: Re: [PATCH v3 3/3] powerpc/32: Add KASAN support To: Dmitry Vyukov References: <935f9f83393affb5d55323b126468ecb90373b88.1547289808.git.christophe.leroy@c-s.fr> <8d433501-a5a7-8e3b-03f7-ccdd0f8622e1@c-s.fr> From: Christophe Leroy Message-ID: Date: Mon, 21 Jan 2019 10:30:55 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Aneesh Kumar K.V" , LKML , Nicholas Piggin , Linux-MM , Paul Mackerras , kasan-dev , Andrey Ryabinin , Alexander Potapenko , linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Le 21/01/2019 à 10:24, Dmitry Vyukov a écrit : > On Mon, Jan 21, 2019 at 9:37 AM Christophe Leroy > wrote: >> >> >> >> Le 21/01/2019 à 09:30, Dmitry Vyukov a écrit : >>> On Mon, Jan 21, 2019 at 8:17 AM Christophe Leroy >>> wrote: >>>> >>>> >>>> >>>> Le 15/01/2019 à 18:23, Andrey Ryabinin a écrit : >>>>> >>>>> >>>>> On 1/12/19 2:16 PM, Christophe Leroy wrote: >>>>> >>>>>> +KASAN_SANITIZE_early_32.o := n >>>>>> +KASAN_SANITIZE_cputable.o := n >>>>>> +KASAN_SANITIZE_prom_init.o := n >>>>>> + >>>>> >>>>> Usually it's also good idea to disable branch profiling - define DISABLE_BRANCH_PROFILING >>>>> either in top of these files or via Makefile. Branch profiling redefines if() statement and calls >>>>> instrumented ftrace_likely_update in every if(). >>>>> >>>>> >>>>> >>>>>> diff --git a/arch/powerpc/mm/kasan_init.c b/arch/powerpc/mm/kasan_init.c >>>>>> new file mode 100644 >>>>>> index 000000000000..3edc9c2d2f3e >>>>> >>>>>> +void __init kasan_init(void) >>>>>> +{ >>>>>> + struct memblock_region *reg; >>>>>> + >>>>>> + for_each_memblock(memory, reg) >>>>>> + kasan_init_region(reg); >>>>>> + >>>>>> + pr_info("KASAN init done\n"); >>>>> >>>>> Without "init_task.kasan_depth = 0;" kasan will not repot bugs. >>>>> >>>>> There is test_kasan module. Make sure that it produce reports. >>>>> >>>> >>>> Thanks for the review. >>>> >>>> Now I get the following very early in boot, what does that mean ? >>> >>> This looks like an instrumented memset call before kasan shadow is >>> mapped, or kasan shadow is not zeros. Does this happen before or after >>> mapping of kasan_early_shadow_page? >> >> This is after the mapping of kasan_early_shadow_page. >> >>> This version seems to miss what x86 code has to clear the early shadow: >>> >>> /* >>> * kasan_early_shadow_page has been used as early shadow memory, thus >>> * it may contain some garbage. Now we can clear and write protect it, >>> * since after the TLB flush no one should write to it. >>> */ >>> memset(kasan_early_shadow_page, 0, PAGE_SIZE); >> >> In the early part, kasan_early_shadow_page is mapped read-only so I >> assumed this reset of its content was unneccessary. >> >> I'll try with it. >> >> Christophe > > As far as I understand machine memory contains garbage after boot, and > that page needs to be all 0's so we need to explicitly memset it. That page is in BSS so it is zeroed before kasan_early_init(). Though as expected, that memset() doesn't fix the issue. Indeed the problem is in kasan_init() : memblock_phys_alloc() doesn't zeroize the allocated memory. I changed it to memblock_alloc() and now it works. Thanks for your help, Christophe > > >>>> [ 0.000000] KASAN init done >>>> [ 0.000000] >>>> ================================================================== >>>> [ 0.000000] BUG: KASAN: unknown-crash in memblock_alloc_try_nid+0xd8/0xf0 >>>> [ 0.000000] Write of size 68 at addr c7ff5a90 by task swapper/0 >>>> [ 0.000000] >>>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted >>>> 5.0.0-rc2-s3k-dev-00559-g88aa407c4bce #772 >>>> [ 0.000000] Call Trace: >>>> [ 0.000000] [c094ded0] [c016c7e4] >>>> print_address_description+0x1a0/0x2b8 (unreliable) >>>> [ 0.000000] [c094df00] [c016caa0] kasan_report+0xe4/0x168 >>>> [ 0.000000] [c094df40] [c016b464] memset+0x2c/0x4c >>>> [ 0.000000] [c094df60] [c08731f0] memblock_alloc_try_nid+0xd8/0xf0 >>>> [ 0.000000] [c094df90] [c0861f20] mmu_context_init+0x58/0xa0 >>>> [ 0.000000] [c094dfb0] [c085ca70] start_kernel+0x54/0x400 >>>> [ 0.000000] [c094dff0] [c0002258] start_here+0x44/0x9c >>>> [ 0.000000] >>>> [ 0.000000] >>>> [ 0.000000] Memory state around the buggy address: >>>> [ 0.000000] c7ff5980: e2 a1 87 81 bd d4 a5 b5 f8 8d 89 e7 72 bc 20 24 >>>> [ 0.000000] c7ff5a00: e7 b9 c1 c7 17 e9 b4 bd a4 d0 e7 a0 11 15 a5 b5 >>>> [ 0.000000] >c7ff5a80: b5 e1 83 a5 2d 65 31 3f f3 e5 a7 ef 34 b5 69 b5 >>>> [ 0.000000] ^ >>>> [ 0.000000] c7ff5b00: 21 a5 c1 c1 b4 bf 2d e5 e5 c3 f5 91 e3 b8 a1 34 >>>> [ 0.000000] c7ff5b80: ad ef 23 87 3d a6 ad b5 c3 c3 80 b7 ac b1 1f 37 >>>> [ 0.000000] >>>> ================================================================== >>>> [ 0.000000] Disabling lock debugging due to kernel taint >>>> [ 0.000000] MMU: Allocated 76 bytes of context maps for 16 contexts >>>> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 8176 >>>> [ 0.000000] Kernel command line: console=ttyCPM0,115200N8 >>>> ip=192.168.2.7:192.168.2.2::255.0.0.0:vgoip:eth0:off kgdboc=ttyCPM0 >>>> [ 0.000000] Dentry cache hash table entries: 16384 (order: 2, 65536 >>>> bytes) >>>> [ 0.000000] Inode-cache hash table entries: 8192 (order: 1, 32768 bytes) >>>> [ 0.000000] Memory: 99904K/131072K available (7376K kernel code, 528K >>>> rwdata, 1168K rodata, 576K init, 4623K bss, 31168K reserved, 0K >>>> cma-reserved) >>>> [ 0.000000] Kernel virtual memory layout: >>>> [ 0.000000] * 0xffefc000..0xffffc000 : fixmap >>>> [ 0.000000] * 0xf7c00000..0xffc00000 : kasan shadow mem >>>> [ 0.000000] * 0xf7a00000..0xf7c00000 : consistent mem >>>> [ 0.000000] * 0xf7a00000..0xf7a00000 : early ioremap >>>> [ 0.000000] * 0xc9000000..0xf7a00000 : vmalloc & ioremap >>>> >>>> >>>> Christophe