From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] powerpc/32: add stack protector support
Date: Fri, 28 Sep 2018 11:26:25 -0500 [thread overview]
Message-ID: <20180928162625.GT23155@gate.crashing.org> (raw)
In-Reply-To: <8736ttu6fs.fsf@concordia.ellerman.id.au>
On Fri, Sep 28, 2018 at 10:56:07PM +1000, Michael Ellerman wrote:
> The problem of low entropy at boot on systems without a good hardware
> source is sort of unsolvable.
>
> As you say it's up to the core kernel/random code, we shouldn't be
> trying to do anything tricky in the arch code.
>
> You don't want your system to take 3 hours to boot because it's waiting
> for entropy for the stack canary.
>
> If we can update the canary later once the entropy pool is setup that
> would be ideal.
Yup, I agree with all that.
But we should *also* not say "oh, there may be cases where we cannot
do the right thing, so just do not even try, ever, anywhere".
Segher
prev parent reply other threads:[~2018-09-28 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 11:40 [PATCH v4 1/2] powerpc/32: add stack protector support Christophe Leroy
2018-09-26 11:40 ` [PATCH v4 2/2] powerpc/64: " Christophe Leroy
2018-09-26 19:16 ` [PATCH v4 1/2] powerpc/32: " Segher Boessenkool
2018-09-27 6:20 ` Christophe LEROY
2018-09-27 7:45 ` Segher Boessenkool
2018-09-27 11:51 ` Christophe LEROY
2018-09-28 12:56 ` Michael Ellerman
2018-09-28 16:26 ` Segher Boessenkool [this message]
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=20180928162625.GT23155@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).