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  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 May 2019 00:48:47 +0800
From:   Hsin-Yi Wang <>
To:     Rob Herring <>
        "" <>,
        Frank Rowand <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Andrew Morton <>,
        Mike Rapoport <>,
        Ard Biesheuvel <>,
        Miles Chen <>,
        James Morse <>,
        Andrew Murray <>,
        Mark Rutland <>,
        Jun Yao <>, Yu Zhao <>,
        Robin Murphy <>,
        Laura Abbott <>,
        Stephen Boyd <>,
        Kees Cook <>
Subject: Re: [PATCH v3 2/3] arm64: implement update_fdt_pgprot()

On Thu, May 16, 2019 at 11:32 PM Rob Herring <> wrote:

> Doesn't kexec operate on a copy because it already does modifications.
Hi Rob,

This patch is to assist "[PATCH v3 3/3] fdt: add support for rng-seed"
( I thought that by default
second kernel would use original fdt, so I write new seed back to
original fdt. Might be wrong.

** "[PATCH v3 3/3] fdt: add support for rng-seed" is supposed to
handle for adding new seed in kexec case, discussed in v2

By default (not considering user defines their own fdt), if second
kernel uses copied fdt, when is it copied and can we modify that?


Powered by blists - more mailing lists