linux-kernel - Re: [PATCH] of/fdt: move elfcorehdr reservation early for crash dump kernel

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]

Date:   Fri, 28 Jan 2022 09:32:59 -0600
From:   Rob Herring <robh+dt@...nel.org>
To:     nikhil.gupta@....com
Cc:     linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Frank Rowand <frowand.list@...il.com>,
        devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Priyanka Jain <priyanka.jain@....com>,
        Dong Aisheng <aisheng.dong@....com>
Subject: Re: [PATCH] of/fdt: move elfcorehdr reservation early for crash dump kernel

On Thu, Jan 27, 2022 at 10:23 PM <nikhil.gupta@....com> wrote:
>
> From: Nikhil Gupta <nikhil.gupta@....com>
>
> elfcorehdr_addr is fixed address passed to Second kernel which may be conflicted
> with potential reserved memory in Second kernel,so fdt_reserve_elfcorehdr() ahead
> of fdt_init_reserved_mem() can relieve this situation.

How does changing the order help exactly? If you have an overlap, that
seems bad no matter what. What if the overlapping reserved area is
used by another core or firmware?

Rob