From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 60652] New: arch/x86/kvm/svm.c: svm_vcpu_reset() and uninitialized dummy variable?
Date: Mon, 29 Jul 2013 21:22:58 +0000 [thread overview]
Message-ID: <bug-60652-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=60652
Bug ID: 60652
Summary: arch/x86/kvm/svm.c: svm_vcpu_reset() and uninitialized
dummy variable?
Product: Virtualization
Version: unspecified
Kernel Version: 3.11rc2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: mikko.rapeli@iki.fi
Regression: No
Coverity CID 751495 feels a bit like a false positive. Is the dummy variable
not initialized on purpose?
1196static void svm_vcpu_reset(struct kvm_vcpu *vcpu)
1197{
1198 struct vcpu_svm *svm = to_svm(vcpu);
1. var_decl: Declaring variable "dummy" without initializer.
1199 u32 dummy;
1200 u32 eax = 1;
1201
1202 init_vmcb(svm);
1203
CID 751495 (#1 of 1): Uninitialized scalar variable (UNINIT)
2. uninit_use_in_call: Using uninitialized value "dummy" when calling
"kvm_cpuid(struct kvm_vcpu *, u32 *, u32 *, u32 *, u32 *)". [hide details]
1204 kvm_cpuid(vcpu, &eax, &dummy, &dummy, &dummy);
/arch/x86/kvm/cpuid.c
646void kvm_cpuid(struct kvm_vcpu *vcpu, u32 *eax, u32 *ebx, u32 *ecx, u32
*edx)
647{
1. read_parm: Reading a parameter value.
648 u32 function = *eax, index = *ecx;
649 struct kvm_cpuid_entry2 *best;
650
651 best = kvm_find_cpuid_entry(vcpu, function, index);
652
653 if (!best)
654 best = check_cpuid_limit(vcpu, function, index);
655
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-07-29 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 21:22 bugzilla-daemon [this message]
2013-11-13 16:34 ` [Bug 60652] arch/x86/kvm/svm.c: svm_vcpu_reset() and uninitialized dummy variable? bugzilla-daemon
2013-11-13 16:35 ` 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-60652-28872@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