From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: borntraeger@de.ibm.com, david@redhat.com,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, frankja@linux.ibm.com,
akrowiak@linux.ibm.com, pasic@linux.ibm.com
Subject: Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first
Date: Fri, 1 Feb 2019 11:50:41 +0100 [thread overview]
Message-ID: <20190201115041.04797c4c.cohuck@redhat.com> (raw)
In-Reply-To: <1549014725-28216-2-git-send-email-pmorel@linux.ibm.com>
On Fri, 1 Feb 2019 10:52:05 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> The case when the SIE for guest3 is not setup for using
> encryption keys nor Adjunct processor but the guest2
> does use these features was not properly handled.
>
> This leads SIE entry for guest3 to crash with validity intercept
> because the guest2, not having the use of encryption keys nor
> Adjunct Processor did not initialize the CRYCB designation.
>
> In the case where none of ECA_APIE, ECB3_AES or ECB3_DEA
> are set in guest3 a format 0 CRYCB is allowed for guest3
> and the CRYCB designation in the SIE for guest3 is not checked
> on SIE entry.
>
> Let's allow the CRYCD designation to be ignored when the
s/CRYCD/CRYCB/
> SIE for guest3 is not initialized for encryption key usage
> nor AP.
>
> Fixup: d6f6959 (KVM: s390: vsie: Do the CRYCB validation first)
I think the canonical format is
Fixes: d6f6959ac587 ("KVM: s390: vsie: Do the CRYCB validation first")
>
CC: stable@vger.kernel.org # 4.20+
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> Reported-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> arch/s390/kvm/vsie.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/s390/kvm/vsie.c b/arch/s390/kvm/vsie.c
> index a153257..a748f76 100644
> --- a/arch/s390/kvm/vsie.c
> +++ b/arch/s390/kvm/vsie.c
> @@ -300,6 +300,9 @@ static int shadow_crycb(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page)
> if (!apie_h && !key_msk)
> return 0;
>
> + if (!(scb_o->eca & ECA_APIE) && !(scb_o->ecb3 & (ECB3_AES | ECB3_DEA)))
> + return 0;
> +
> if (!crycb_addr)
> return set_validity_icpt(scb_s, 0x0039U);
>
Looks sane to me, but I'll let vsie experts comment.
next prev parent reply other threads:[~2019-02-01 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 9:52 [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first Pierre Morel
2019-02-01 9:52 ` Pierre Morel
2019-02-01 10:50 ` Cornelia Huck [this message]
2019-02-01 13:36 ` Pierre Morel
2019-02-01 10:56 ` David Hildenbrand
2019-02-01 13:37 ` Pierre Morel
2019-02-04 14:48 ` Christian Borntraeger
2019-02-04 16:18 ` Pierre Morel
2019-02-04 15:15 ` David Hildenbrand
2019-02-04 16:17 ` Pierre Morel
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=20190201115041.04797c4c.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.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).