From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>, KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 10/11] KVM: s390: sthyi: remove invalid guest write access
Date: Mon, 28 Aug 2017 13:39:47 +0200 [thread overview]
Message-ID: <20170828133947.261f607c.cohuck@redhat.com> (raw)
In-Reply-To: <1503907651-65296-4-git-send-email-borntraeger@de.ibm.com>
On Mon, 28 Aug 2017 10:07:30 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> handle_sthyi() always writes to guest memory if the sthyi function
> code is zero in order to fault in the page that later is written to.
>
> However a function code of zero does not necessarily mean that a write
> to guest memory happens: if the KVM host is running as a second level
> guest under z/VM 6.2 the sthyi instruction is indicated to be
> available to the KVM host, however if the instruction is executed it
> will always return with a return code that indicates "unsupported
> function code".
>
> In such a case handle_sthyi() must not write to guest memory. This
> means that the prior write access to fault in the guest page may
> result in invalid guest exceptions, and/or invalid data modification.
>
> In order to be architecture compliant simply remove the write_guest()
> call.
>
> Given that the guest assumed a write access anyway, this fix does not
> qualify for -stable. This just makes sure the sthyi handler is
> architecture compliant.
>
> Fixes: 95ca2cb57985 ("KVM: s390: Add sthyi emulation")
> Reviewed-by: Janosch Frank <frankja@linux.vnet.ibm.com>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> arch/s390/kvm/sthyi.c | 8 --------
> 1 file changed, 8 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2017-08-28 11:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 8:07 [PATCH 00/11] KVM: s390: Fixes and features for 4.14 Christian Borntraeger
2017-08-28 8:07 ` [PATCH 05/11] KVM: s390: Support Configuration z/Architecture Mode Christian Borntraeger
2017-08-28 9:07 ` Cornelia Huck
2017-08-28 9:11 ` Christian Borntraeger
2017-08-28 9:14 ` Christian Borntraeger
2017-08-28 11:33 ` Cornelia Huck
2017-08-28 11:35 ` Cornelia Huck
2017-08-28 14:06 ` David Hildenbrand
2017-08-28 14:24 ` Christian Borntraeger
2017-08-28 14:38 ` David Hildenbrand
2017-08-28 14:42 ` Christian Borntraeger
2017-08-28 19:27 ` David Hildenbrand
2017-08-28 19:35 ` Christian Borntraeger
2017-08-28 19:38 ` Christian Borntraeger
2017-08-28 19:42 ` David Hildenbrand
2017-08-29 7:18 ` Christian Borntraeger
2017-08-29 12:08 ` David Hildenbrand
2017-08-29 12:21 ` Christian Borntraeger
2017-08-29 12:24 ` David Hildenbrand
2017-08-29 14:31 ` [PATCH] KVM: s390: we are always in czam mode David Hildenbrand
2017-08-29 14:40 ` Cornelia Huck
2017-08-29 14:48 ` Christian Borntraeger
2017-08-28 19:41 ` [PATCH 05/11] KVM: s390: Support Configuration z/Architecture Mode David Hildenbrand
2017-08-28 8:07 ` [PATCH 06/11] KVM: s390: Multiple Epoch Facility support Christian Borntraeger
2017-08-28 11:21 ` Cornelia Huck
2017-08-28 11:36 ` Christian Borntraeger
2017-08-28 11:45 ` Cornelia Huck
2017-08-29 12:24 ` David Hildenbrand
2017-08-29 12:46 ` Christian Borntraeger
2017-08-29 12:54 ` David Hildenbrand
2017-08-29 12:59 ` Christian Borntraeger
2017-08-28 8:07 ` [PATCH 10/11] KVM: s390: sthyi: remove invalid guest write access Christian Borntraeger
2017-08-28 11:39 ` Cornelia Huck [this message]
2017-08-28 8:07 ` [PATCH 11/11] KVM: s390: expose no-DAT to guest and migration support Christian Borntraeger
2017-08-28 12:12 ` Cornelia Huck
2017-08-28 12:17 ` [PATCH 00/11] KVM: s390: Fixes and features for 4.14 Cornelia Huck
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=20170828133947.261f607c.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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