linux-kernel - Re: [PATCH] arm64: move kimage

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]

Message-ID: <e87d4a759618c13dfc9d814112e6352a@remlab.net>
Date:   Thu, 12 Mar 2020 18:42:35 +0200
From:   Remi Denis-Courmont <remi@...lab.net>
To:     Mark Rutland <mark.rutland@....com>
Cc:     linux-arm-kernel@...ts.infradead.org, suzuki.poulose@....com,
        maz@...nel.org, linux-kernel@...r.kernel.org, james.morse@....com,
        catalin.marinas@....com, will@...nel.org,
        kvmarm@...ts.cs.columbia.edu, julien.thierry.kdev@...il.com,
        ard.biesheuvel@...aro.org
Subject: Re: [PATCH] arm64: move kimage_vaddr to .rodata

Le 2020-03-12 18:40, Mark Rutland a écrit :
> On Thu, Mar 12, 2020 at 11:40:02AM +0200, Rémi Denis-Courmont wrote:
>> From: Remi Denis-Courmont <remi.denis.courmont@...wei.com>
>> 
>> This datum is not referenced from .idmap.text: it does not need to be
>> mapped in idmap. Lets move it to .rodata as it is never written to 
>> after
>> early boot of the primary CPU.
>> (Maybe .data.ro_after_init would be cleaner though?)
> 
> Can we move this into arch/arm64/mm/mmu.c, where we already have
> kimage_voffset:
> 
> | u64 kimage_voffset __ro_after_init;
> | EXPORT_SYMBOL(kimage_voffset);
> 
> ... or is it not possible to initialize kimage_vaddr correctly in C?

Good question... I'll check tomorrow.

-- 
Rémi Denis-Courmont