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
| ||
|
Date: Wed, 29 Apr 2020 18:01:33 +0100 From: James Morse <james.morse@....com> To: Pavel Tatashin <pasha.tatashin@...een.com> Cc: jmorris@...ei.org, sashal@...nel.org, ebiederm@...ssion.com, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, corbet@....net, catalin.marinas@....com, will@...nel.org, linux-arm-kernel@...ts.infradead.org, maz@...nel.org, vladimir.murzin@....com, matthias.bgg@...il.com, bhsharma@...hat.com, linux-mm@...ck.org, mark.rutland@....com, steve.capper@....com, rfontana@...hat.com, tglx@...utronix.de, selindag@...il.com Subject: Re: [PATCH v9 09/18] arm64: kexec: call kexec_image_info only once Hi Pavel, On 26/03/2020 03:24, Pavel Tatashin wrote: > Currently, kexec_image_info() is called during load time, and > right before kernel is being kexec'ed. There is no need to do both. I think the original logic was if debugging, you'd see the load-time value in dmesg, and the kexec-time values when the machine panic()d and you hadn't made a note of the previous set. But I'm not sure why you'd have these debug messages enabled unless you were debugging kexec. > So, call it only once when segments are loaded and the physical > location of page with copy of arm64_relocate_new_kernel is known. Sure, keep the earlier version that is more likely to be seen. Acked-by: James Morse <james.morse@....com> Thanks, James
Powered by blists - more mailing lists