Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-04 Thread Pierre Morel
On 04/02/2019 15:48, Christian Borntraeger wrote: On 01.02.2019 14:37, Pierre Morel wrote: On 01/02/2019 11:56, David Hildenbrand wrote: On 01.02.19 10:52, Pierre Morel wrote: The case when the SIE for guest3 is not setup for using encryption keys nor Adjunct processor but the guest2 does us

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-04 Thread Pierre Morel
On 04/02/2019 16:15, David Hildenbrand wrote: On 01.02.19 14:37, Pierre Morel wrote: On 01/02/2019 11:56, David Hildenbrand wrote: On 01.02.19 10:52, Pierre Morel wrote: The case when the SIE for guest3 is not setup for using encryption keys nor Adjunct processor but the guest2 does use these

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-04 Thread David Hildenbrand
On 01.02.19 14:37, Pierre Morel wrote: > On 01/02/2019 11:56, David Hildenbrand wrote: >> On 01.02.19 10:52, Pierre Morel 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.

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-04 Thread Christian Borntraeger
On 01.02.2019 14:37, Pierre Morel wrote: > On 01/02/2019 11:56, David Hildenbrand wrote: >> On 01.02.19 10:52, Pierre Morel 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 han

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread Pierre Morel
On 01/02/2019 11:56, David Hildenbrand wrote: On 01.02.19 10:52, Pierre Morel 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 valid

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread Pierre Morel
On 01/02/2019 11:50, Cornelia Huck wrote: On Fri, 1 Feb 2019 10:52:05 +0100 Pierre Morel 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 cr

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread David Hildenbrand
On 01.02.19 10:52, Pierre Morel 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

Re: [PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread Cornelia Huck
On Fri, 1 Feb 2019 10:52:05 +0100 Pierre Morel 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 > becau

[PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread Pierre Morel
This is a BUGFIX Surely must be CC stable. Pierre Morel (1): KVM: s390: vsie: fix Do the CRYCB validation first arch/s390/kvm/vsie.c | 3 +++ 1 file changed, 3 insertions(+) -- 2.7.4

[PATCH v1] KVM: s390: vsie: fix Do the CRYCB validation first

2019-02-01 Thread Pierre Morel
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 Proc