From: Kees Cook <keescook@chromium.org>
To: "Peter Zijlstra (Intel)" <peterz@infradead.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Eric Biggers <ebiggers@kernel.org>, x86 <x86@kernel.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [tip: sched/urgent] sched: Fix RANDSTRUCT build fail
Date: Fri, 19 Jun 2020 20:13:59 -0700 [thread overview]
Message-ID: <202006192008.337CB5212E@keescook> (raw)
In-Reply-To: <159178525684.17951.17825196124597318263.tip-bot2@tip-bot2>
On Wed, Jun 10, 2020 at 10:34:16AM -0000, tip-bot2 for Peter Zijlstra wrote:
> The following commit has been merged into the sched/urgent branch of tip:
>
> Commit-ID: bfb9fbe0f7e70ec5c8e51ee55b6968d4dff14456
> Gitweb: https://git.kernel.org/tip/bfb9fbe0f7e70ec5c8e51ee55b6968d4dff14456
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Wed, 10 Jun 2020 12:14:09 +02:00
> Committer: Peter Zijlstra <peterz@infradead.org>
> CommitterDate: Wed, 10 Jun 2020 12:30:19 +02:00
>
> sched: Fix RANDSTRUCT build fail
>
> As a temporary build fix, the proper cleanup needs more work.
>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Reported-by: Eric Biggers <ebiggers@kernel.org>
> Suggested-by: Eric Biggers <ebiggers@kernel.org>
> Suggested-by: Kees Cook <keescook@chromium.org>
> Fixes: a148866489fb ("sched: Replace rq::wake_list")
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Hi, can this please get sent to Linus before -rc2? With a148866489fb in
-rc1, all the CI with the GCC plugins installed have been failing their
all*config builds. This entered -next 9 days ago (and fixed the -next
builds), but Linus's tree is still failing:
https://kernelci.org/build/mainline/branch/master/kernel/v5.8-rc1-226-g4333a9b0b67b/
...
https://kernelci.org/build/mainline/branch/master/kernel/v5.8-rc1/
Thanks!
-Kees
> ---
> include/linux/sched.h | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 57a5ce9..59caeb9 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -653,8 +653,10 @@ struct task_struct {
> unsigned int ptrace;
>
> #ifdef CONFIG_SMP
> - struct llist_node wake_entry;
> - unsigned int wake_entry_type;
> + struct {
> + struct llist_node wake_entry;
> + unsigned int wake_entry_type;
> + };
> int on_cpu;
> #ifdef CONFIG_THREAD_INFO_IN_TASK
> /* Current CPU: */
--
Kees Cook
next prev parent reply other threads:[~2020-06-20 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 10:34 [tip: sched/urgent] sched: Fix RANDSTRUCT build fail tip-bot2 for Peter Zijlstra
2020-06-20 3:13 ` Kees Cook [this message]
2020-06-20 16:32 ` Linus Torvalds
2020-06-22 8:10 ` Peter Zijlstra
2020-06-22 8:16 ` Peter Zijlstra
2020-06-22 8:18 ` Peter Zijlstra
2020-06-22 14:36 ` Guenter Roeck
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=202006192008.337CB5212E@keescook \
--to=keescook@chromium.org \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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