kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 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/1] KVM: s390: fix for 4.9 (via kvm/master)
Date: Thu, 20 Oct 2016 20:47:20 +0200	[thread overview]
Message-ID: <20161020184720.GA17270@potion> (raw)
In-Reply-To: <1476987606-123515-1-git-send-email-borntraeger@de.ibm.com>

2016-10-20 20:20+0200, Christian Borntraeger:
> Paolo, Radim,
> 
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
> 
>   Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git  tags/kvm-s390-master-4.9-1
> 
> for you to fetch changes up to a5efb6b6c99a3a6dc4330f51d8066f638bdea0ac:
> 
>   KVM: s390: reject invalid modes for runtime instrumentation (2016-10-20 20:06:12 +0200)

Pulled, thanks.

> ----------------------------------------------------------------
> KVM: s390: Fix for user-triggerable WARN_ON
> 
> A malicious user space can provide an invalid mode for runtime
> instrumentation via the interfaces that are normally used on
> the target host during migration. This would trigger a WARN_ON
> via validity intercept. Let's detect this special case.
> 
> ----------------------------------------------------------------
> Christian Borntraeger (1):
>       KVM: s390: reject invalid modes for runtime instrumentation
> 
>  arch/s390/kvm/intercept.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 

  parent reply	other threads:[~2016-10-20 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 18:20 [GIT PULL 0/1] KVM: s390: fix for 4.9 (via kvm/master) Christian Borntraeger
2016-10-20 18:20 ` [GIT PULL 1/1] KVM: s390: reject invalid modes for runtime instrumentation Christian Borntraeger
2016-10-20 18:42 ` [GIT PULL 0/1] KVM: s390: fix for 4.9 (via kvm/master) Radim Krčmář
2016-10-20 18:47 ` Radim Krčmář [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-27  8:07 [GIT PULL 0/1] KVM: s390: Fix " Christian Borntraeger
2016-10-27  9:37 ` Paolo Bonzini

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=20161020184720.GA17270@potion \
    --to=rkrcmar@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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).