From: "tip-bot2 for Borislav Petkov" <tip-bot2@linutronix.de> To: linux-tip-commits@vger.kernel.org Cc: Sergei Trofimovich <slyfox@gentoo.org>, Borislav Petkov <bp@suse.de>, Nick Desaulniers <ndesaulniers@google.com>, Kees Cook <keescook@chromium.org>, x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org> Subject: [tip: x86/build] x86: Fix early boot crash on gcc-10, next try Date: Mon, 27 Apr 2020 11:37:48 -0000 Message-ID: <158798746828.28353.6010675315553653459.tip-bot2@tip-bot2> (raw) In-Reply-To: <20200314164451.346497-1-slyfox@gentoo.org> The following commit has been merged into the x86/build branch of tip: Commit-ID: f670269a42bfdd2c83a1118cc3d1b475547eac22 Gitweb: https://git.kernel.org/tip/f670269a42bfdd2c83a1118cc3d1b475547eac22 Author: Borislav Petkov <bp@suse.de> AuthorDate: Wed, 22 Apr 2020 18:11:30 +02:00 Committer: Borislav Petkov <bp@suse.de> CommitterDate: Mon, 27 Apr 2020 13:32:04 +02:00 x86: Fix early boot crash on gcc-10, next try ... or the odyssey of trying to disable the stack protector for the function which generates the stack canary value. The whole story started with Sergei reporting a boot crash with a kernel built with gcc-10: Kernel panic — not syncing: stack-protector: Kernel stack is corrupted in: start_secondary CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.6.0-rc5—00235—gfffb08b37df9 #139 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H77M—D3H, BIOS F12 11/14/2013 Call Trace: dump_stack panic ? start_secondary __stack_chk_fail start_secondary secondary_startup_64 -—-[ end Kernel panic — not syncing: stack—protector: Kernel stack is corrupted in: start_secondary This happens because gcc-10 tail-call optimizes the last function call in start_secondary() - cpu_startup_entry() - and thus emits a stack canary check which fails because the canary value changes after the boot_init_stack_canary() call. To fix that, the initial attempt was to mark the one function which generates the stack canary with: __attribute__((optimize("-fno-stack-protector"))) ... start_secondary(void *unused) however, using the optimize attribute doesn't work cumulatively as the attribute does not add to but rather replaces previously supplied optimization options - roughly all -fxxx options. The key one among them being -fno-omit-frame-pointer and thus leading to not present frame pointer - frame pointer which the kernel needs. The next attempt to prevent compilers from tail-call optimizing the last function call cpu_startup_entry(), shy of carving out start_secondary() into a separate compilation unit and building it with -fno-stack-protector, is this one. The current solution is short and sweet, and reportedly, is supported by both compilers so let's see how far we'll get this time. Reported-by: Sergei Trofimovich <slyfox@gentoo.org> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Reviewed-by: Kees Cook <keescook@chromium.org> Link: https://lkml.kernel.org/r/20200314164451.346497-1-slyfox@gentoo.org --- arch/x86/include/asm/stackprotector.h | 7 ++++++- arch/x86/kernel/smpboot.c | 8 ++++++++ arch/x86/xen/smp_pv.c | 1 + include/linux/compiler.h | 6 ++++++ 4 files changed, 21 insertions(+), 1 deletion(-) diff --git a/arch/x86/include/asm/stackprotector.h b/arch/x86/include/asm/stackprotector.h index 91e29b6..9804a79 100644 --- a/arch/x86/include/asm/stackprotector.h +++ b/arch/x86/include/asm/stackprotector.h @@ -55,8 +55,13 @@ /* * Initialize the stackprotector canary value. * - * NOTE: this must only be called from functions that never return, + * NOTE: this must only be called from functions that never return * and it must always be inlined. + * + * In addition, it should be called from a compilation unit for which + * stack protector is disabled. Alternatively, the caller should not end + * with a function call which gets tail-call optimized as that would + * lead to checking a modified canary value. */ static __always_inline void boot_init_stack_canary(void) { diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c index fe3ab96..4f275ac 100644 --- a/arch/x86/kernel/smpboot.c +++ b/arch/x86/kernel/smpboot.c @@ -266,6 +266,14 @@ static void notrace start_secondary(void *unused) wmb(); cpu_startup_entry(CPUHP_AP_ONLINE_IDLE); + + /* + * Prevent tail call to cpu_startup_entry() because the stack protector + * guard has been changed a couple of function calls up, in + * boot_init_stack_canary() and must not be checked before tail calling + * another function. + */ + prevent_tail_call_optimization(); } /** diff --git a/arch/x86/xen/smp_pv.c b/arch/x86/xen/smp_pv.c index 8fb8a50..f2adb63 100644 --- a/arch/x86/xen/smp_pv.c +++ b/arch/x86/xen/smp_pv.c @@ -93,6 +93,7 @@ asmlinkage __visible void cpu_bringup_and_idle(void) cpu_bringup(); boot_init_stack_canary(); cpu_startup_entry(CPUHP_AP_ONLINE_IDLE); + prevent_tail_call_optimization(); } void xen_smp_intr_free_pv(unsigned int cpu) diff --git a/include/linux/compiler.h b/include/linux/compiler.h index 034b0a6..732754d 100644 --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -356,4 +356,10 @@ static inline void *offset_to_ptr(const int *off) /* &a[0] degrades to a pointer: a different type from an array */ #define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0])) +/* + * This is needed in functions which generate the stack canary, see + * arch/x86/kernel/smpboot.c::start_secondary() for an example. + */ +#define prevent_tail_call_optimization() asm("") + #endif /* __LINUX_COMPILER_H */
next prev parent reply index Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-14 16:44 [PATCH] x86: fix early boot crash on gcc-10 Sergei Trofimovich 2020-03-16 13:04 ` Peter Zijlstra 2020-03-16 13:26 ` Jakub Jelinek 2020-03-16 13:42 ` Peter Zijlstra 2020-03-16 17:54 ` Borislav Petkov 2020-03-16 18:03 ` Jakub Jelinek 2020-03-17 14:36 ` Borislav Petkov 2020-03-17 14:39 ` Jakub Jelinek 2020-03-17 14:49 ` Borislav Petkov 2020-03-17 16:35 ` David Laight 2020-03-25 13:31 ` Borislav Petkov 2020-03-26 21:54 ` Sergei Trofimovich 2020-03-26 22:35 ` Borislav Petkov 2020-03-28 8:48 ` [PATCH v2] " Sergei Trofimovich 2020-04-13 14:15 ` [tip: x86/urgent] x86: Fix " tip-bot2 for Sergei Trofimovich 2020-04-13 16:35 ` [PATCH v2] x86: fix " Borislav Petkov 2020-04-14 13:50 ` Michael Matz 2020-04-15 7:48 ` Borislav Petkov 2020-04-15 14:53 ` Michael Matz 2020-04-15 22:19 ` Sergei Trofimovich 2020-04-17 7:57 ` Borislav Petkov 2020-04-17 8:07 ` Jakub Jelinek 2020-04-17 8:42 ` Borislav Petkov 2020-04-17 8:58 ` Jakub Jelinek 2020-04-17 9:09 ` Borislav Petkov 2020-04-17 18:15 ` Nick Desaulniers 2020-04-17 18:22 ` Nick Desaulniers 2020-04-17 19:06 ` Jakub Jelinek 2020-04-17 19:49 ` Nick Desaulniers 2020-04-17 19:53 ` Nick Desaulniers 2020-04-20 14:04 ` Michael Matz 2020-04-22 10:23 ` Borislav Petkov 2020-04-22 11:40 ` Peter Zijlstra 2020-04-22 13:49 ` Borislav Petkov 2020-04-22 13:55 ` Jakub Jelinek 2020-04-22 14:16 ` Martin Liška 2020-04-22 15:06 ` Michael Matz 2020-04-22 16:53 ` Borislav Petkov 2020-04-22 17:02 ` Jakub Jelinek 2020-04-22 18:47 ` Nick Desaulniers 2020-04-22 18:55 ` Nick Desaulniers 2020-04-22 19:21 ` Borislav Petkov 2020-04-22 21:05 ` Nick Desaulniers 2020-04-22 21:26 ` Borislav Petkov 2020-04-22 22:57 ` Nick Desaulniers 2020-04-23 12:53 ` Borislav Petkov 2020-04-23 16:12 ` [PATCH] x86: Fix early boot crash on gcc-10, next try Borislav Petkov 2020-04-23 17:30 ` Borislav Petkov 2020-04-23 18:02 ` Nick Desaulniers 2020-04-23 18:27 ` Borislav Petkov 2020-04-27 11:37 ` [tip: x86/build] x86/build: Check whether the compiler is sane tip-bot2 for Borislav Petkov 2020-04-23 19:40 ` [PATCH] x86: Fix early boot crash on gcc-10, next try Kees Cook 2020-04-25 1:46 ` Arvind Sankar 2020-04-25 8:57 ` Borislav Petkov 2020-04-25 11:09 ` Jürgen Groß 2020-04-25 15:04 ` Arvind Sankar 2020-04-25 17:31 ` Borislav Petkov 2020-04-25 17:52 ` Borislav Petkov 2020-04-27 17:07 ` David Laight 2020-04-25 18:37 ` Segher Boessenkool 2020-04-25 18:53 ` Borislav Petkov 2020-04-25 19:15 ` Segher Boessenkool 2020-04-25 22:17 ` Borislav Petkov 2020-04-25 22:25 ` Arvind Sankar 2020-04-17 10:38 ` [PATCH v2] x86: fix early boot crash on gcc-10 Peter Zijlstra 2020-04-18 13:12 ` David Laight 2020-04-17 10:41 ` Peter Zijlstra 2020-03-16 18:20 ` [PATCH] " Arvind Sankar 2020-03-16 18:54 ` Arvind Sankar 2020-03-16 19:53 ` Arvind Sankar 2020-03-16 20:08 ` Jakub Jelinek 2020-03-16 20:40 ` Arvind Sankar 2020-03-16 22:12 ` Sergei Trofimovich 2020-03-17 11:46 ` Jakub Jelinek 2020-03-17 18:10 ` Sergei Trofimovich 2020-03-16 18:22 ` Arvind Sankar 2020-03-26 23:16 ` [PATCH v2] " Sergei Trofimovich 2020-04-27 11:37 ` tip-bot2 for Borislav Petkov [this message] 2020-05-15 11:20 ` [tip: x86/urgent] x86: Fix early boot crash on gcc-10, third try tip-bot2 for Borislav Petkov
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=158798746828.28353.6010675315553653459.tip-bot2@tip-bot2 \ --to=tip-bot2@linutronix.de \ --cc=bp@suse.de \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tip-commits@vger.kernel.org \ --cc=ndesaulniers@google.com \ --cc=slyfox@gentoo.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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ linux-kernel@vger.kernel.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git