From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>, Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] kbuild: add '-fno-stack-check' to barebox build options
Date: Tue, 16 Mar 2021 20:10:45 +0100 [thread overview]
Message-ID: <f639c838-e999-7a9b-ed03-7fd46c9e6fad@pengutronix.de> (raw)
In-Reply-To: <20210224084945.GI5549@pengutronix.de>
Hello Sascha,
On 24.02.21 09:49, Sascha Hauer wrote:
> On Tue, Feb 23, 2021 at 08:24:26AM +0100, Ahmad Fatoum wrote:
>> This ports over Linux commit 3ce120b16cc5 ("kbuild: add
>> '-fno-stack-check' to kernel build options"):
>>
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>>
>> kbuild: add '-fno-stack-check' to kernel build options
>>
>> It appears that hardened gentoo enables "-fstack-check" by default for
>> gcc.
>>
>> That doesn't work _at_all_ for the kernel, because the kernel stack
>> doesn't act like a user stack at all: it's much smaller, and it doesn't
>> auto-expand on use. So the extra "probe one page below the stack" code
>> generated by -fstack-check just breaks the kernel in horrible ways,
>> causing infinite double faults etc.
>>
>> [ I have to say, that the particular code gcc generates looks very
>> stupid even for user space where it works, but that's a separate
>> issue. ]
>>
>> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>>
>> I am porting it, because it may become more acute with the incoming
>> support for multiple stacks (via initjmp).
>>
>> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
>> ---
>
> Applied, thanks
Can't find both patches in next.
Cheers,
Ahmad
>
> Sascha
>
>> Makefile | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/Makefile b/Makefile
>> index f3c85cff9430..fa7fbbeb35f0 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -622,6 +622,9 @@ KBUILD_CFLAGS += $(call cc-option, -fno-delete-null-pointer-checks,)
>> # disable invalid "can't wrap" optimizations for signed / pointers
>> KBUILD_CFLAGS += $(call cc-option,-fno-strict-overflow)
>>
>> +# Make sure -fstack-check isn't enabled (like gentoo apparently did)
>> +KBUILD_CFLAGS += $(call cc-option,-fno-stack-check)
>> +
>> KBUILD_CFLAGS += $(call cc-disable-warning, address-of-packed-member)
>>
>> # Align the bit size of userspace programs with the kernel
>> --
>> 2.30.0
>>
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-03-16 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 7:24 Ahmad Fatoum
2021-02-23 7:24 ` [PATCH 2/2] kbuild: add '-fcf-protection=none' " Ahmad Fatoum
2021-02-24 8:49 ` [PATCH 1/2] kbuild: add '-fno-stack-check' " Sascha Hauer
2021-03-16 19:10 ` Ahmad Fatoum [this message]
2021-03-22 5:12 ` Sascha Hauer
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=f639c838-e999-7a9b-ed03-7fd46c9e6fad@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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