From: Peter Zijlstra <peterz@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ingo Molnar <mingo@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
linux-next@vger.kernel.org
Subject: Re: Fw: next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68)
Date: Fri, 5 Jun 2020 16:47:59 +0200 [thread overview]
Message-ID: <20200605144759.GG4117@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <202006050734.97C4AB35CF@keescook>
On Fri, Jun 05, 2020 at 07:36:02AM -0700, Kees Cook wrote:
> On Fri, Jun 05, 2020 at 10:38:55AM +0200, Peter Zijlstra wrote:
> > On Fri, Jun 05, 2020 at 11:52:13AM +1000, Stephen Rothwell wrote:
> > > Commit
> > >
> > > a148866489fb ("sched: Replace rq::wake_list")
> > >
> > > added
> > >
> > > BUILD_BUG_ON(offsetof(struct task_struct, wake_entry_type) - offsetof(struct task_struct, wake_entry) !=
> > > offsetof(struct __call_single_data, flags) - offsetof(struct __call_single_data, llist));
> > >
> > > in kernel/smp.c. This seems to be failing - at least for gcc-8 (I
> > > haven't seen any failures in my linux-next testing).
> >
> > CONFIG_GCC_PLUGIN_RANDSTRUCT=y
>
> (FWIW, the plugins will only be enabled if the gcc plugins-dev package is
> installed)
Which I hadn't, which is why I'd never seen it. I have now.
> > working on it.
>
> Either of these solutions should fix it. I'm not sure which is
> preferred.
I posted in another thread that had earlier raised the issue:
https://lkml.kernel.org/r/20200605093704.GB2948@hirez.programming.kicks-ass.net
prev parent reply other threads:[~2020-06-05 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:52 Fw: next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68) Stephen Rothwell
2020-06-05 8:38 ` Peter Zijlstra
2020-06-05 14:36 ` Kees Cook
2020-06-05 14:47 ` Peter Zijlstra [this message]
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=20200605144759.GG4117@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bot@kernelci.org \
--cc=keescook@chromium.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
/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