From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
linux-hardening@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: mainline build failure of powerpc allmodconfig for prom_init_check
Date: Mon, 18 Jul 2022 09:56:01 -0500 [thread overview]
Message-ID: <20220718145601.GE25951@gate.crashing.org> (raw)
In-Reply-To: <87k08bdqm1.fsf@mpe.ellerman.id.au>
On Mon, Jul 18, 2022 at 01:52:38PM +1000, Michael Ellerman wrote:
> Segher Boessenkool <segher@kernel.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
next prev parent reply other threads:[~2022-07-18 15:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 8:55 mainline build failure of powerpc allmodconfig for prom_init_check Sudip Mukherjee (Codethink)
2022-07-17 9:12 ` Sudip Mukherjee
2022-07-17 14:44 ` Linus Torvalds
2022-07-17 19:54 ` Segher Boessenkool
2022-07-18 3:52 ` Michael Ellerman
2022-07-18 14:56 ` Segher Boessenkool [this message]
2022-07-17 20:25 ` Sudip Mukherjee
2022-07-17 20:29 ` Linus Torvalds
2022-07-17 20:38 ` Sudip Mukherjee
2022-07-17 20:56 ` Linus Torvalds
2022-07-17 20:56 ` Segher Boessenkool
2022-07-17 21:11 ` Linus Torvalds
2022-07-17 21:45 ` Segher Boessenkool
2022-07-18 1:38 ` Linus Torvalds
2022-07-18 4:41 ` Michael Ellerman
2022-07-18 7:51 ` David Laight
2022-07-18 13:44 ` [PATCH] powerpc/64s: Disable stack variable initialisation for prom_init Michael Ellerman
2022-07-18 15:03 ` Sudip Mukherjee
2022-07-18 18:34 ` Linus Torvalds
2022-07-18 19:06 ` mainline build failure of powerpc allmodconfig for prom_init_check Linus Torvalds
2022-07-18 22:08 ` Segher Boessenkool
2022-07-18 22:55 ` Linus Torvalds
2022-07-19 13:35 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220718145601.GE25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).