diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2016-04-13 10:09:47 +0200 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2016-06-10 12:07:28 +0200 |
| commit | 6164a2e90a5b6c5c32ccfe7a1baff80d603d702d (patch) | |
| tree | e228ebab5b999145ff8b018d43a979915c03bcae /crypto/crypto_user.c | |
| parent | fe69eabf8deb85ae8b2958830ea3b2911e332820 (diff) | |
KVM: s390: pfmf: fix end address calculation
The current calculation is wrong if absolute != real address. Let's just
calculate the start address for 4k frames upfront. Otherwise, the
calculated end address will be wrong, resulting in wrong memory
location/storage keys getting touched.
To keep low-address protection working (using the effective address),
we have to move the check.
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'crypto/crypto_user.c')
0 files changed, 0 insertions, 0 deletions