From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207173] kvm compiling problem 5.6.x kvm_main.c:2236:42: error: ‘nr_pages_avail’ may be used uninitialized in this function
Date: Tue, 14 Apr 2020 09:19:13 +0000 [thread overview]
Message-ID: <bug-207173-28872-DjwhAi3k9z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207173-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207173
--- Comment #3 from zoran.davidovac@gmail.com ---
Yes all 5.6.X (up to 4 tested) before it was while loop now there is for loop
and some other changes in kvm code vs 5.5.x kernel that compiles with same
code,
and yes always reproducible.
Standard gcc 9.2 now 9.3
https://drive.google.com/open?id=18NDMqounXy6RwNhRxTJDUizTckm7QBOR
I do not see any other way to add file except paste it encode it ?
# make bzImage
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC arch/x86/kvm/../../../virt/kvm/kvm_main.o
arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function
‘__kvm_gfn_to_hva_cache_init’:
arch/x86/kvm/../../../virt/kvm/kvm_main.c:2236:42: error: ‘nr_pages_avail’ may
be used uninitialized in this function [-Werror=maybe-uninitialized]
2236 | for ( ; start_gfn <= end_gfn; start_gfn += nr_pages_avail) {
| ~~~~~~~~~~^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [scripts/Makefile.build:268:
arch/x86/kvm/../../../virt/kvm/kvm_main.o] Error 1
make[1]: *** [scripts/Makefile.build:505: arch/x86/kvm] Error 2
make: *** [Makefile:1683: arch/x86] Error 2
root@host:/usr/src/linux-5.6.4#
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-14 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 14:25 [Bug 207173] New: kvm compiling problem 5.6.x kvm_main.c:2236:42: error: ‘nr_pages_avail’ may be used uninitialized in this function bugzilla-daemon
2020-04-12 7:28 ` [Bug 207173] " bugzilla-daemon
2020-04-13 23:41 ` bugzilla-daemon
2020-04-14 9:19 ` bugzilla-daemon [this message]
2020-04-14 15:37 ` bugzilla-daemon
2020-04-14 18:53 ` bugzilla-daemon
2020-04-15 1:19 ` bugzilla-daemon
2020-04-15 5:43 ` bugzilla-daemon
2020-04-26 2:10 ` bugzilla-daemon
2020-04-27 16:45 ` bugzilla-daemon
2020-05-10 2:04 ` bugzilla-daemon
2020-05-12 10:30 ` bugzilla-daemon
2020-05-12 14:37 ` bugzilla-daemon
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=bug-207173-28872-DjwhAi3k9z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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 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).