From: Andi Kleen <ak@linux.intel.com>
To: peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: [PATCH] sched: Work around undefined behavior in sched class checking
Date: Tue, 4 May 2021 20:39:45 -0700 [thread overview]
Message-ID: <20210505033945.1282851-1-ak@linux.intel.com> (raw)
From: Andi Kleen <andi@firstfloor.org>
The scheduler initialization code checks that the scheduling
classes are consecutive in memory by comparing the end
addresses with the next address.
Technically in ISO C comparing symbol addresseses outside different objects
is undefined. With LTO gcc 10 tries to exploits this and creates an
unconditional BUG_ON in the scheduler initialization, resulting
in a boot hang.
Use RELOC_HIDE to make this work. This hides the symbols from gcc,
so the optimizer won't make these assumption. I also split
the BUG_ONs in multiple.
Signed-off-by: Andi Kleen <andi@firstfloor.org>
---
kernel/sched/core.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 98191218d891..272a654f5293 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -8086,12 +8086,20 @@ void __init sched_init(void)
unsigned long ptr = 0;
int i;
- /* Make sure the linker didn't screw up */
- BUG_ON(&idle_sched_class + 1 != &fair_sched_class ||
- &fair_sched_class + 1 != &rt_sched_class ||
- &rt_sched_class + 1 != &dl_sched_class);
+ /*
+ * Make sure the linker didn't screw up.
+ * We have to use RELOC_HIDE to prevent gcc from optimizing
+ * them to true because they're technically undefined in ISO-C.
+ */
+ BUG_ON(RELOC_HIDE(&idle_sched_class, 0) + 1 !=
+ RELOC_HIDE(&fair_sched_class, 0));
+ BUG_ON(RELOC_HIDE(&fair_sched_class, 0) + 1 !=
+ RELOC_HIDE(&rt_sched_class, 0));
+ BUG_ON(RELOC_HIDE(&rt_sched_class, 0) + 1 !=
+ RELOC_HIDE(&dl_sched_class, 0));
#ifdef CONFIG_SMP
- BUG_ON(&dl_sched_class + 1 != &stop_sched_class);
+ BUG_ON(RELOC_HIDE(&dl_sched_class, 0) + 1 !=
+ RELOC_HIDE(&stop_sched_class, 0));
#endif
wait_bit_init();
--
2.25.4
next reply other threads:[~2021-05-05 3:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 3:39 Andi Kleen [this message]
2021-05-05 6:46 ` [PATCH] sched: Work around undefined behavior in sched class checking Peter Zijlstra
2021-05-05 8:47 ` Florian Weimer
2021-05-05 9:04 ` Peter Zijlstra
2021-05-05 14:39 ` Andi Kleen
2021-05-05 16:41 ` Nick Desaulniers
2021-05-05 16:48 ` Andi Kleen
2021-05-05 17:08 ` Nick Desaulniers
2021-05-05 17:20 ` Andi Kleen
2021-05-05 14:34 ` Andi Kleen
2021-05-05 15:34 ` Peter Zijlstra
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=20210505033945.1282851-1-ak@linux.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.