From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
linux-next@vger.kernel.org
Subject: Fw: next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68)
Date: Fri, 5 Jun 2020 11:52:13 +1000 [thread overview]
Message-ID: <20200605115213.2836fccf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3031 bytes --]
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).
The pending-fixes branch in linux-next isjust Linus' tree plus the
branches of fixes for Linus' tree.
Begin forwarded message:
Date: Thu, 04 Jun 2020 18:15:15 -0700 (PDT)
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68)
next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68)
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.7-8671-g086779e58c68/
Tree: next
Branch: pending-fixes
Git Describe: v5.7-8671-g086779e58c68
Git Commit: 086779e58c6867c3f8488d6729e267094a0cd826
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Built: 7 unique architectures
Build Failures Detected:
arm64:
allmodconfig: (gcc-8) FAIL
x86_64:
allmodconfig: (gcc-8) FAIL
Errors summary:
1 include/linux/compiler.h:403:38: error: call to ‘__compiletime_assert_399’ declared with attribute error: BUILD_BUG_ON failed: 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)
1 include/linux/compiler.h:403:38: error: call to ‘__compiletime_assert_134’ declared with attribute error: BUILD_BUG_ON failed: 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)
--------------------------------------------------------------------------------
allmodconfig (arm64, gcc-8) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
include/linux/compiler.h:403:38: error: call to ‘__compiletime_assert_134’ declared with attribute error: BUILD_BUG_ON failed: 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)
--------------------------------------------------------------------------------
allmodconfig (x86_64, gcc-8) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
include/linux/compiler.h:403:38: error: call to ‘__compiletime_assert_399’ declared with attribute error: BUILD_BUG_ON failed: 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)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-06-05 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:52 Stephen Rothwell [this message]
2020-06-05 8:38 ` Fw: next/pending-fixes build: 162 builds: 2 failed, 160 passed, 2 errors, 109 warnings (v5.7-8671-g086779e58c68) Peter Zijlstra
2020-06-05 14:36 ` Kees Cook
2020-06-05 14:47 ` 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=20200605115213.2836fccf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bot@kernelci.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox