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
| ||
|
Message-ID: <20220718145601.GE25951@gate.crashing.org> Date: Mon, 18 Jul 2022 09:56:01 -0500 From: Segher Boessenkool <segher@...nel.crashing.org> To: Michael Ellerman <mpe@...erman.id.au> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Sudip Mukherjee <sudipm.mukherjee@...il.com>, Kees Cook <keescook@...omium.org>, linux-kernel <linux-kernel@...r.kernel.org>, Paul Mackerras <paulus@...ba.org>, linux-hardening@...r.kernel.org, linuxppc-dev <linuxppc-dev@...ts.ozlabs.org> Subject: Re: mainline build failure of powerpc allmodconfig for prom_init_check On Mon, Jul 18, 2022 at 01:52:38PM +1000, Michael Ellerman wrote: > Segher Boessenkool <segher@...nel.crashing.org> writes: > > Can't we simply have a small simple implementation of these functions in > > arch/powerpc/boot/? This stuff is not performance-critical, and this is > > not the first time we hit these problems. > > prom_init.c isn't in arch/powerpc/boot :) Ah duh :-) > It's linked into the kernel proper, but we want it to behave like a > pre-boot environment (because not all boot paths run it) which is why we > restrict what symbols it can call. > > We could have a prom_memset() etc. but we'd need to do some tricks to > rewrite references to memset() to prom_memset() before linking. You can do it in its linker script? Segher
Powered by blists - more mailing lists