From: "tip-bot2 for ndesaulniers@google.com" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Nathan Chancellor <nathan@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: objtool/core] start_kernel: Omit prevent_tail_call_optimization() for newer toolchains
Date: Thu, 18 May 2023 11:08:03 -0000 [thread overview]
Message-ID: <168440808364.404.15005624206596163176.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230412-no_stackp-v2-2-116f9fe4bbe7@google.com>
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: dc1d05536f44cee16e46e86316e6718b2c0d8872
Gitweb: https://git.kernel.org/tip/dc1d05536f44cee16e46e86316e6718b2c0d8872
Author: ndesaulniers@google.com <ndesaulniers@google.com>
AuthorDate: Mon, 17 Apr 2023 15:00:06 -07:00
Committer: Josh Poimboeuf <jpoimboe@kernel.org>
CommitterDate: Tue, 16 May 2023 06:28:24 -07:00
start_kernel: Omit prevent_tail_call_optimization() for newer toolchains
prevent_tail_call_optimization() was added in
commit a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try")
to work around stack canaries getting inserted into functions that would
initialize the stack canary in the first place.
Now that we have no_stack_protector function attribute (gcc-11+,
clang-7+) and use it on start_kernel(), remove the call to
prevent_tail_call_optimization() such that we may one day remove it
outright.
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Link: https://lore.kernel.org/r/20230412-no_stackp-v2-2-116f9fe4bbe7@google.com
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
---
init/main.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/init/main.c b/init/main.c
index c445c1f..c0b6499 100644
--- a/init/main.c
+++ b/init/main.c
@@ -1088,7 +1088,13 @@ void start_kernel(void)
/* Do the rest non-__init'ed, we're now alive */
arch_call_rest_init();
+ /*
+ * Avoid stack canaries in callers of boot_init_stack_canary for gcc-10
+ * and older.
+ */
+#if !__has_attribute(__no_stack_protector__)
prevent_tail_call_optimization();
+#endif
}
/* Call all constructor functions linked into the kernel. */
next prev parent reply other threads:[~2023-05-18 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 22:00 [PATCH v2 0/2] start_kernel: omit stack canary ndesaulniers
2023-04-17 22:00 ` [PATCH v2 1/2] start_kernel: add no_stack_protector fn attr ndesaulniers
2023-05-18 11:08 ` [tip: objtool/core] start_kernel: Add __no_stack_protector function attribute tip-bot2 for ndesaulniers@google.com
2023-05-19 17:11 ` David Vernet
2023-05-19 17:18 ` Nick Desaulniers
2023-05-19 17:42 ` David Vernet
2023-04-17 22:00 ` [PATCH v2 2/2] start_kernel: omit prevent_tail_call_optimization for newer toolchains ndesaulniers
2023-05-18 11:08 ` tip-bot2 for ndesaulniers@google.com [this message]
2023-04-18 21:38 ` [PATCH v2 0/2] start_kernel: omit stack canary Josh Poimboeuf
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=168440808364.404.15005624206596163176.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®