kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	David Hildenbrand <dahi@linux.vnet.ibm.com>
Cc: KVM <kvm@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 0/5] KVM: s390: Fixes for 4.4
Date: Thu, 19 Nov 2015 18:06:34 +0100	[thread overview]
Message-ID: <564E019A.3000404@redhat.com> (raw)
In-Reply-To: <1447942166-66514-1-git-send-email-borntraeger@de.ibm.com>



On 19/11/2015 15:09, Christian Borntraeger wrote:
> Paolo,
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git  tags/kvm-s390-master-4.4-1
> 
> for you to fetch changes up to 152e9f65d66f0a3891efc3869440becc0e7ff53f:
> 
>   KVM: s390: fix wrong lookup of VCPUs by array index (2015-11-19 14:47:43 +0100)
> 
> ----------------------------------------------------------------
> KVM: s390: Fixes for 4.4
> 
> 1. disallow changing the SIMD mode when CPUs have been created.
>    it allowed userspace to corrupt kernel memory
> 2. Fix vCPU lookup. Until now the vCPU number equals the vCPU id. Some
>    kernel code places relied on that. This might
>    a: cause guest failures
>    b: allow userspace to corrupt kernel memory
> 3. Fencing of the PFMF instruction should use the guest facilities
>    and not the host facilities.
> 
> ----------------------------------------------------------------
> David Hildenbrand (4):
>       KVM: s390: enable SIMD only when no VCPUs were created
>       KVM: Provide function for VCPU lookup by id
>       KVM: s390: avoid memory overwrites on emergency signal injection
>       KVM: s390: fix wrong lookup of VCPUs by array index
> 
> Heiko Carstens (1):
>       KVM: s390: fix pfmf intercept handler
> 
>  arch/s390/kvm/interrupt.c |  7 +++++--
>  arch/s390/kvm/kvm-s390.c  |  6 +++++-
>  arch/s390/kvm/priv.c      |  2 +-
>  arch/s390/kvm/sigp.c      |  8 ++------
>  include/linux/kvm_host.h  | 11 +++++++++++
>  5 files changed, 24 insertions(+), 10 deletions(-)
> 

Pulled, thanks (for now to kvm/next, since that's what Stephen Rothwell
tests daily).

Paolo

      parent reply	other threads:[~2015-11-19 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 14:09 [GIT PULL 0/5] KVM: s390: Fixes for 4.4 Christian Borntraeger
2015-11-19 14:09 ` [GIT PULL 1/5] KVM: s390: enable SIMD only when no VCPUs were created Christian Borntraeger
2015-11-19 14:09 ` [GIT PULL 2/5] KVM: s390: fix pfmf intercept handler Christian Borntraeger
2015-11-19 14:09 ` [GIT PULL 3/5] KVM: Provide function for VCPU lookup by id Christian Borntraeger
2015-11-19 14:09 ` [GIT PULL 4/5] KVM: s390: avoid memory overwrites on emergency signal injection Christian Borntraeger
2015-11-19 14:09 ` [GIT PULL 5/5] KVM: s390: fix wrong lookup of VCPUs by array index Christian Borntraeger
2015-11-19 17:06 ` Paolo Bonzini [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=564E019A.3000404@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@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).