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  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]
Date:   Fri, 17 Jul 2020 08:32:13 +0200
From:   Arnd Bergmann <>
To:     Atish Patra <>
Cc:     "" <>,
        Anup Patel <>,
        Ard Biesheuvel <>,
        Greentime Hu <>,
        Kees Cook <>,
        linux-efi <>,,
        Mark Rutland <>,
        Masahiro Yamada <>,
        Mike Rapoport <>,
        Palmer Dabbelt <>,
        Paul Walmsley <>,
        Will Deacon <>, Zong Li <>,
        Heinrich Schuchardt <>,
        Linux ARM <>
Subject: Re: [RFT PATCH v3 1/9] RISC-V: Move DT mapping outof fixmap

On Fri, Jul 17, 2020 at 1:41 AM Atish Patra <> wrote:
> From: Anup Patel <>
> Currently, RISC-V reserves 1MB of fixmap memory for device tree. However,
> it maps only single PMD (2MB) space for fixmap which leaves only < 1MB space
> left for other kernel features such as early ioremap which requires fixmap
> as well. The fixmap size can be increased by another 2MB but it brings
> additional complexity and changes the virtual memory layout as well.
> If we require some additional feature requiring fixmap again, it has to be
> moved again.
> Technically, DT doesn't need a fixmap as the memory occupied by the DT is
> only used during boot. Thus, init memory section can be used for the same
> purpose as well. This simplifies fixmap implementation.
> Signed-off-by: Anup Patel <>
> Signed-off-by: Atish Patra <>

The patch seems fine for the moment, but I have one concern for the
long run:

> +#define DTB_EARLY_SIZE         SZ_1M
> +static char early_dtb[DTB_EARLY_SIZE] __initdata;

Hardcoding the size in .bss seems slightly problematic both for
small and for big systems. On machines with very little memory,
this can lead to running out of free pages before .initdata gets freed,
and it increases the size of the uncompressed vmlinux file by quite
a bit.

On some systems, the 1MB limit may get too small. While most dtbs
would fall into the range between 10KB and 100KB, it can also be
much larger than that, e.g. when there are DT properties that include
blobs like device firmware that gets loaded into hardware by a kernel

Is there anything stopping you from parsing the FDT in its original
location without the extra copy before it gets unflattened?


Powered by blists - more mailing lists