summaryrefslogtreecommitdiffstats
path: root/arch/s390/tools
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2018-03-06 14:27:58 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2018-03-06 13:33:02 +0000
commitf07afa0462b76a5b9c4f3a43d5ac24fdb86a90c2 (patch)
tree6cae764e4102fa96ce68876229c6bd8d21bc8d0e /arch/s390/tools
parent09a0fb67536a49af19f2bfc632100e9de91fe526 (diff)
downloadlinux-stable-f07afa0462b76a5b9c4f3a43d5ac24fdb86a90c2.tar.gz
linux-stable-f07afa0462b76a5b9c4f3a43d5ac24fdb86a90c2.tar.bz2
linux-stable-f07afa0462b76a5b9c4f3a43d5ac24fdb86a90c2.zip
KVM: s390: fix memory overwrites when not using SCA entries
Even if we don't have extended SCA support, we can have more than 64 CPUs if we don't enable any HW features that might use the SCA entries. Now, this works just fine, but we missed a return, which is why we would actually store the SCA entries. If we have more than 64 CPUs, this means writing outside of the basic SCA - bad. Let's fix this. This allows > 64 CPUs when running nested (under vSIE) without random crashes. Fixes: a6940674c384 ("KVM: s390: allow 255 VCPUs when sca entries aren't used") Reported-by: Christian Borntraeger <borntraeger@de.ibm.com> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: David Hildenbrand <david@redhat.com> Message-Id: <20180306132758.21034-1-david@redhat.com> Cc: stable@vger.kernel.org Reviewed-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'arch/s390/tools')
0 files changed, 0 insertions, 0 deletions