All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: kvm@vger.kernel.org
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, Neil Brown <neilb@suse.de>
Subject: [PATCH] kvm: Fix off by one in kvm_for_each_vcpu iteration
Date: Tue, 12 Apr 2011 21:30:17 -0400	[thread overview]
Message-ID: <4DA4FCA9.9070508@suse.com> (raw)

 This patch avoids gcc issuing the following warning when KVM_MAX_VCPUS=1:
 warning: array subscript is above array bounds

 kvm_for_each_vcpu currently checks to see if the index for the vcpu is
 valid /after/ loading it. We don't run into problems because the address
 is still inside the enclosing struct kvm and we never deference or write
 to it, so this isn't a security issue.

 The warning occurs when KVM_MAX_VCPUS=1 because the increment portion of
 the loop will *always* cause the loop to load an invalid location since
 ++idx will always be > 0.

 This patch moves the load so that the check occurs before the load and
 we don't run into the compiler warning.

Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
---
 include/linux/kvm_host.h |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -292,9 +292,10 @@ static inline struct kvm_vcpu *kvm_get_v
 }
 
 #define kvm_for_each_vcpu(idx, vcpup, kvm) \
-	for (idx = 0, vcpup = kvm_get_vcpu(kvm, idx); \
-	     idx < atomic_read(&kvm->online_vcpus) && vcpup; \
-	     vcpup = kvm_get_vcpu(kvm, ++idx))
+	for (idx = 0; \
+	     idx < atomic_read(&kvm->online_vcpus) && \
+	     (vcpup = kvm_get_vcpu(kvm, idx)) != NULL; \
+	     idx++)
 
 int kvm_vcpu_init(struct kvm_vcpu *vcpu, struct kvm *kvm, unsigned id);
 void kvm_vcpu_uninit(struct kvm_vcpu *vcpu);
-- 
Jeff Mahoney
SUSE Labs

             reply	other threads:[~2011-04-13  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  1:30 Jeff Mahoney [this message]
2011-04-17  9:11 ` [PATCH] kvm: Fix off by one in kvm_for_each_vcpu iteration Avi Kivity

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=4DA4FCA9.9070508@suse.com \
    --to=jeffm@suse.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=neilb@suse.de \
    /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.