From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
KVM <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: linux-next: Tree for Jun 9 (<linux/kvm_host.h>)
Date: Wed, 9 Jun 2021 15:17:09 -0700 [thread overview]
Message-ID: <c7320562-dbee-cd98-cc40-d5522933aaa7@infradead.org> (raw)
In-Reply-To: <20210609225703.56bfcc12@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
On 6/9/21 5:57 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210608:
>
on i386:
In file included from <command-line>:0:0:
In function ‘__gfn_to_hva_memslot’,
inlined from ‘__gfn_to_hva_many.part.67’ at ../arch/x86/kvm/../../../virt/kvm/kvm_main.c:1910:9,
inlined from ‘__gfn_to_hva_many’:
./../include/linux/compiler_types.h:328:38: error: call to ‘__compiletime_assert_235’ declared with attribute error: BUILD_BUG_ON failed: sizeof(_i) > sizeof(long)
_compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
^
./../include/linux/compiler_types.h:309:4: note: in definition of macro ‘__compiletime_assert’
prefix ## suffix(); \
^~~~~~
./../include/linux/compiler_types.h:328:2: note: in expansion of macro ‘_compiletime_assert’
_compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
^~~~~~~~~~~~~~~~~~~
../include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’
#define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
^~~~~~~~~~~~~~~~~~
../include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’
BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
^~~~~~~~~~~~~~~~
../include/linux/nospec.h:57:2: note: in expansion of macro ‘BUILD_BUG_ON’
BUILD_BUG_ON(sizeof(_i) > sizeof(long)); \
^~~~~~~~~~~~
../include/linux/kvm_host.h:1194:25: note: in expansion of macro ‘array_index_nospec’
unsigned long offset = array_index_nospec(gfn - slot->base_gfn,
^~~~~~~~~~~~~~~~~~
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r9874.gz --]
[-- Type: application/gzip, Size: 33432 bytes --]
prev parent reply other threads:[~2021-06-09 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:57 linux-next: Tree for Jun 9 Stephen Rothwell
2021-06-09 22:00 ` linux-next: Tree for Jun 9 (net/netfilter/nfnetlink_hook.c) Randy Dunlap
2021-06-09 22:02 ` Pablo Neira Ayuso
2021-06-09 22:17 ` Randy Dunlap [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=c7320562-dbee-cd98-cc40-d5522933aaa7@infradead.org \
--to=rdunlap@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).