From: Tony Lindgren <tony@atomide.com>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: Kees Cook <keescook@chromium.org>,
Nicolas Pitre <nico@fluxnic.net>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-omap <linux-omap@vger.kernel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
"Arthur D." <spinal.by@gmail.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Nokia N900 on 5.4 and 5.5
Date: Fri, 7 Feb 2020 08:53:44 -0800 [thread overview]
Message-ID: <20200207165344.GB64767@atomide.com> (raw)
In-Reply-To: <da14d6bb-f241-2dd4-8e94-886217a40ed7@wizzup.org>
* 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.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
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 08:53:44 -0800 [thread overview]
Message-ID: <20200207165344.GB64767@atomide.com> (raw)
In-Reply-To: <da14d6bb-f241-2dd4-8e94-886217a40ed7@wizzup.org>
* 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.
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 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 14:54 Nokia N900 on 5.4 and 5.5 Merlijn Wajer
2020-02-07 15:51 ` H. Nikolaus Schaller
2020-02-07 16:36 ` Tony Lindgren
2020-02-07 16:36 ` Tony Lindgren
2020-02-07 16:48 ` Merlijn Wajer
2020-02-07 16:48 ` Merlijn Wajer
2020-02-07 16:53 ` Tony Lindgren [this message]
2020-02-07 16:53 ` Tony Lindgren
2020-02-07 17:01 ` Tony Lindgren
2020-02-07 17:01 ` Tony Lindgren
2020-02-07 20:20 ` Arthur D.
2020-02-07 20:20 ` Arthur D.
2020-02-08 1:49 ` Merlijn Wajer
2020-02-08 1:49 ` Merlijn Wajer
2020-02-13 21:33 ` Ard Biesheuvel
2020-02-13 21:33 ` Ard Biesheuvel
2020-02-13 21:44 ` Tony Lindgren
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=20200207165344.GB64767@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.