From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Hans-Christian Egtvedt (hegtvedt)" <hegtvedt@cisco.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Stable release 4.4.286 broken for ARM64 with CONFIG_CC_STACKPROTECTOR=y
Date: Thu, 7 Oct 2021 08:20:26 +0200 [thread overview]
Message-ID: <YV6RqtU4uLJs5ntR@kroah.com> (raw)
In-Reply-To: <DM5PR11MB001226B8D03B8CC8FA093AC6DDB09@DM5PR11MB0012.namprd11.prod.outlook.com>
On Wed, Oct 06, 2021 at 09:20:42PM +0000, Hans-Christian Egtvedt (hegtvedt) wrote:
> Hello,
>
> latest stable release 4.4.286 does not build for me on ARM64 with
> CONFIG_CC_STACKPROTECTOR=y.
>
> The offending commit
>
> commit 69e450b170995e8a4e3eb94fb14c822553124870
> Author: Dan Li <ashimida@linux.alibaba.com>
> Date: Tue Sep 14 11:44:02 2021
>
> arm64: Mark __stack_chk_guard as __ro_after_init
>
> The 4.4.y kernel does not have the ro_after_init section defined at all,
> stable kernel 4.9.y is the first to have it.
>
> I do not have an overview of this feature, but it appears to have
> started with commit
>
> commit c74ba8b3480da6ddaea17df2263ec09b869ac496
> Author: Kees Cook <keescook@chromium.org>
> Date: Wed Feb 17 23:41:15 2016
>
> arch: Introduce post-init read-only memory
>
> --
> Best regards, Hans-Christian Noren Egtvedt.
Thank you for letting me know. I'll go revert this and do a new release
with this fixed.
greg k-h
prev parent reply other threads:[~2021-10-07 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 21:20 Stable release 4.4.286 broken for ARM64 with CONFIG_CC_STACKPROTECTOR=y Hans-Christian Egtvedt (hegtvedt)
2021-10-07 6:20 ` Greg Kroah-Hartman [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=YV6RqtU4uLJs5ntR@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hegtvedt@cisco.com \
--cc=stable@vger.kernel.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 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.