linux-kernel - of_reserved_mem()/kexec interaction

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <DB6PR0402MB2727C7111A5BDBB07F05E29886550@DB6PR0402MB2727.eurprd04.prod.outlook.com>
Date:   Mon, 1 Apr 2019 19:09:02 +0000
From:   Roy Pledge <roy.pledge@....com>
To:     Rob Herring <robh@...nel.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: of_reserved_mem()/kexec interaction

Hi Rob,

Not sure if you're the right person to address this to but if not
hopefully someone on the list can assist me.

I'm trying to understand if memory reserved in the device tree via the
"reserved-memory" facility is preserved during a kexec system call,
i.e., is the memory at the same location with the contents undisturbed
when the new kernel starts?

Thanks

Roy