From: Florian Fainelli <f.fainelli@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>, kernel test robot <lkp@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, keescook@chromium.org,
hjl.tools@gmail.com, linux@rasmusvillemoes.dk
Subject: Re: [sched] c3a340f7e7: invalid_opcode:#[##]
Date: Tue, 20 Oct 2020 16:39:38 -0700 [thread overview]
Message-ID: <58ff47cc-dc55-e383-7a5b-37008d145aba@gmail.com> (raw)
In-Reply-To: <20200630144905.GX4817@hirez.programming.kicks-ass.net>
On 6/30/20 7:49 AM, Peter Zijlstra wrote:
> On Tue, Jun 30, 2020 at 02:46:28PM +0200, Peter Zijlstra wrote:
>> On Mon, Jun 29, 2020 at 08:31:27AM +0800, kernel test robot wrote:
>>> Greeting,
>>>
>>> FYI, we noticed the following commit (built with gcc-4.9):
>>>
>>> commit: c3a340f7e7eadac7662ab104ceb16432e5a4c6b2 ("sched: Have sched_class_highest define by vmlinux.lds.h")
>>
>>> [ 1.840970] kernel BUG at kernel/sched/core.c:6652!
>>
>> W T H
>>
>> $ readelf -Wa defconfig-build/vmlinux | grep sched_class
>> 62931: c1e62d20 0 NOTYPE GLOBAL DEFAULT 2 __begin_sched_classes
>> 65736: c1e62f40 96 OBJECT GLOBAL DEFAULT 2 stop_sched_class
>> 71813: c1e62dc0 96 OBJECT GLOBAL DEFAULT 2 fair_sched_class
>> 78689: c1e62d40 96 OBJECT GLOBAL DEFAULT 2 idle_sched_class
>> 78953: c1e62fa0 0 NOTYPE GLOBAL DEFAULT 2 __end_sched_classes
>> 79090: c1e62e40 96 OBJECT GLOBAL DEFAULT 2 rt_sched_class
>> 79431: c1e62ec0 96 OBJECT GLOBAL DEFAULT 2 dl_sched_class
>>
>> $ printf "%d\n" $((0xc1e62dc0 - 0xc1e62d40))
>> 128
>>
>> So even though the object is 96 bytes in size, has an explicit 32 byte
>> alignment, the array ends up with a stride of 128 bytes !?!?!
>>
>> Consistently so with GCC-4.9. Any other GCC I tried does the sane thing.
>>
>> Full patch included below.
>>
>> Anybody any clue wth 4.9 is doing crazy things like this?
>>
>> ---
>
> This seems to make everything work, it builds and boots for 4.9 and
> builds x86_64-defconfig with clang11 (just to check a !GCC compiler).
Hi Peter,
This patch causes all files under kernel/sched/* that include sched.h to
be rebuilt whenever the value of CONFIG_BLK_DEV_INITRD. There are at
least two build systems (buildroot and OpenWrt) that toggle this
configuration value in order to produce a kernel image without an
initramfs, and one with.
On ARM we get all of these to be needlessly rebuilt:
CC kernel/sched/core.o
CC kernel/sched/loadavg.o
CC kernel/sched/clock.o
CC kernel/sched/cputime.o
CC kernel/sched/idle.o
CC kernel/sched/fair.o
CC kernel/sched/rt.o
CC kernel/sched/deadline.o
CC kernel/sched/wait.o
CC kernel/sched/wait_bit.o
CC kernel/sched/swait.o
CC kernel/sched/completion.o
CC kernel/sched/cpupri.o
CC kernel/sched/cpudeadline.o
CC kernel/sched/topology.o
CC kernel/sched/stop_task.o
CC kernel/sched/pelt.o
CC kernel/sched/debug.o
CC kernel/sched/cpufreq.o
CC kernel/sched/membarrier.o
Short of moving the STRUCT_ALIGNMENT to a separate header that would not
be subject to any configuration key change, can you think of a good way
to avoid these rebuilds, including for architectures like ARM that ship
their own vmlinux.lds.h? I would not say this is a bug, but it is
definitively an inconvenience.
Thanks!
--
Florian
next prev parent reply other threads:[~2020-10-20 23:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 0:31 [sched] c3a340f7e7: invalid_opcode:#[##] kernel test robot
2020-06-29 0:31 ` kernel test robot
2020-06-30 12:46 ` Peter Zijlstra
2020-06-30 12:46 ` Peter Zijlstra
2020-06-30 13:55 ` Rasmus Villemoes
2020-06-30 13:55 ` Rasmus Villemoes
2020-06-30 14:02 ` Peter Zijlstra
2020-06-30 14:02 ` Peter Zijlstra
2020-06-30 14:11 ` Peter Zijlstra
2020-06-30 14:11 ` Peter Zijlstra
2020-06-30 14:35 ` Peter Zijlstra
2020-06-30 14:35 ` Peter Zijlstra
2020-06-30 14:49 ` Peter Zijlstra
2020-06-30 14:49 ` Peter Zijlstra
2020-07-09 8:45 ` [tip: sched/core] sched, vmlinux.lds: Increase STRUCT_ALIGNMENT to 64 bytes for GCC-4.9 tip-bot2 for Peter Zijlstra
2020-10-20 23:39 ` Florian Fainelli [this message]
2020-10-21 8:00 ` GCC section alignment, and GCC-4.9 being a weird one Peter Zijlstra
2020-10-21 13:18 ` Jakub Jelinek
2020-10-21 13:44 ` Peter Zijlstra
2020-10-21 17:42 ` Nick Desaulniers
2020-10-21 17:54 ` Miguel Ojeda
2020-10-21 18:35 ` [Linux-kernel-mentees] " Joe Perches
2020-10-21 18:35 ` Joe Perches
2020-10-21 19:27 ` [Linux-kernel-mentees] " Miguel Ojeda
2020-10-21 19:27 ` Miguel Ojeda
2020-10-22 7:38 ` 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=58ff47cc-dc55-e383-7a5b-37008d145aba@gmail.com \
--to=f.fainelli@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 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.