From: Tony Lindgren <tony@atomide.com>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Kees Cook <keescook@chromium.org>,
Nicolas Pitre <nico@fluxnic.net>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-omap <linux-omap@vger.kernel.org>,
"Arthur D." <spinal.by@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Nokia N900 on 5.4 and 5.5
Date: Fri, 7 Feb 2020 09:01:49 -0800 [thread overview]
Message-ID: <20200207170149.GC64767@atomide.com> (raw)
In-Reply-To: <20200207165344.GB64767@atomide.com>
* Tony Lindgren <tony@atomide.com> [200207 16:54]:
> * Merlijn Wajer <merlijn@wizzup.org> [200207 16:47]:
> > On 07/02/2020 17:36, Tony Lindgren wrote:
> > >
> > > Looks like there's a regression in general for appended dtb booting that
> > > was caused by commit 9f671e58159a ("security: Create "kernel hardening"
> > > config area"). With that change we now get STACKPROTECTOR_PER_TASK
> > > selected by default with Kconfig.
> > >
> > > Merlijn, care to try to disable STACKPROTECTOR_PER_TASK in your
> > > .config to see if that helps?
> >
> > Yes, this makes the kernel boot.
>
> OK good to hear. My guess is that having STACKPROTECTOR_PER_TASK
> selected causes changes to include/generated/asm-offsets.h that
> appended dtb booting does not like. But let's see what others
> think.
I don't think this is an issue of CONFIG_STACKPROTECTOR + CONFIG_SMP
booted on UP machine as it only happens with appended dtb it seems.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-07 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <79b91017-b52a-8aff-4b9c-913ae655f7bf@wizzup.org>
[not found] ` <185CD173-C13C-4D56-B3DE-9A8D7784963C@goldelico.com>
2020-02-07 16:36 ` Nokia N900 on 5.4 and 5.5 Tony Lindgren
2020-02-07 16:48 ` Merlijn Wajer
2020-02-07 16:53 ` Tony Lindgren
2020-02-07 17:01 ` Tony Lindgren [this message]
2020-02-07 20:20 ` Arthur D.
2020-02-08 1:49 ` Merlijn Wajer
2020-02-13 21:33 ` Ard Biesheuvel
2020-02-13 21:44 ` Tony Lindgren
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=20200207170149.GC64767@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=hns@goldelico.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=nico@fluxnic.net \
--cc=rmk+kernel@armlinux.org.uk \
--cc=spinal.by@gmail.com \
/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).