From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: compiler.h:417:38: error: call to '__compiletime_assert_59' declared with attribute error: BUILD_BUG_ON failed: sizeof(_i) > sizeof(long)
Date: Sun, 13 Jun 2021 17:05:09 +0200 [thread overview]
Message-ID: <YMYepbrAxKbgaXi8@kroah.com> (raw)
In-Reply-To: <CA+G9fYuBo_WgjtW1BugKLPeYnmLEe65zU7Ttt=FB2uqMzZy1eQ@mail.gmail.com>
On Sun, Jun 13, 2021 at 08:25:19PM +0530, Naresh Kamboju wrote:
> The following error was noticed on stable-rc 5.12, 5.10, 5.4, 4.19,
> 4.14, 4.9 and 4.4
> for i386 and arm.
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=arm
> CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache
> arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc'
> In file included from /builds/linux/include/linux/kernel.h:11,
> from /builds/linux/include/linux/list.h:9,
> from /builds/linux/include/linux/preempt.h:11,
> from /builds/linux/include/linux/hardirq.h:5,
> from /builds/linux/include/linux/kvm_host.h:7,
> from
> /builds/linux/arch/arm/kvm/../../../virt/kvm/kvm_main.c:18:
> In function '__gfn_to_hva_memslot',
> inlined from '__gfn_to_hva_many.part.6' at
> /builds/linux/arch/arm/kvm/../../../virt/kvm/kvm_main.c:1446:9,
> inlined from '__gfn_to_hva_many' at
> /builds/linux/arch/arm/kvm/../../../virt/kvm/kvm_main.c:1434:22:
> /builds/linux/include/linux/compiler.h:417:38: error: call to
> '__compiletime_assert_59' declared with attribute error: BUILD_BUG_ON
> failed: sizeof(_i) > sizeof(long)
> _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> ^
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ref:
> https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/jobs/1342604370#L389
Odd. Does Linus's tree have this problem?
The only arm changes was in arch/arm/include/asm/cpuidle.h in the tree
right now. There are some kvm changes, but they are tiny...
Can you bisect this?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-13 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 14:55 compiler.h:417:38: error: call to '__compiletime_assert_59' declared with attribute error: BUILD_BUG_ON failed: sizeof(_i) > sizeof(long) Naresh Kamboju
2021-06-13 15:05 ` Greg Kroah-Hartman [this message]
2021-06-14 4:54 ` Naresh Kamboju
2021-06-14 5:18 ` Greg Kroah-Hartman
2021-06-14 6:24 ` Naresh Kamboju
2021-06-14 8:36 ` Greg Kroah-Hartman
2021-06-14 8:40 ` Greg Kroah-Hartman
2021-06-14 9:39 ` Naresh Kamboju
2021-06-14 9:46 ` Greg Kroah-Hartman
2021-06-14 9:56 ` Paolo Bonzini
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=YMYepbrAxKbgaXi8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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.