From: Peter Xu <peterx@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, "Evgeny Yakovlev" <wrfsh@yandex-team.ru>
Subject: Re: [kvm-unit-tests PATCH 0/3] x86: Cleanup max test CPUs
Date: Tue, 10 Sep 2019 15:57:35 +0800 [thread overview]
Message-ID: <20190910075735.GC8696@xz-x1> (raw)
In-Reply-To: <20190906163450.30797-1-sean.j.christopherson@intel.com>
On Fri, Sep 06, 2019 at 09:34:47AM -0700, Sean Christopherson wrote:
> Fix a bug Evgeny reported where init_apic_map() can cause random
> corruption due accessing random bytes far beyond the bounds of
> online_cpus. Take the opportunity to bump the max number of test CPUs
> to a realistic maximum, i.e. what kvm-unit-tests can support without a
> major rework.
>
> Sean Christopherson (3):
> x86: Fix out of bounds access when processing online_cpus
> x86: Declare online_cpus based on MAX_TEST_CPUS
> x86: Bump max number of test CPUs to 255
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2019-09-10 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 16:34 [kvm-unit-tests PATCH 0/3] x86: Cleanup max test CPUs Sean Christopherson
2019-09-06 16:34 ` [kvm-unit-tests PATCH 1/3] x86: Fix out of bounds access when processing online_cpus Sean Christopherson
2019-09-06 16:34 ` [kvm-unit-tests PATCH 2/3] x86: Declare online_cpus based on MAX_TEST_CPUS Sean Christopherson
2019-09-06 16:34 ` [kvm-unit-tests PATCH 3/3] x86: Bump max number of test CPUs to 255 Sean Christopherson
2019-09-10 14:46 ` Paolo Bonzini
2019-09-10 7:57 ` Peter Xu [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=20190910075735.GC8696@xz-x1 \
--to=peterx@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=wrfsh@yandex-team.ru \
/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).