diff options
author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2016-04-12 13:32:25 +0200 |
---|---|---|
committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2016-05-04 10:57:38 +0200 |
commit | 4a5e7e381f9d7ab92fd8f9280683dae11698292e (patch) | |
tree | eff26193d2c08dda6685db3ec9ddaea1cd85fa16 /kernel/irq/spurious.c | |
parent | 05b1159e641fa45e885aec8bf8e515117c8977d9 (diff) | |
download | op-kernel-dev-4a5e7e381f9d7ab92fd8f9280683dae11698292e.zip op-kernel-dev-4a5e7e381f9d7ab92fd8f9280683dae11698292e.tar.gz |
KVM: s390: cmma: don't check entry content
We should never inject an exception after we manually rewound the PSW
(to retry the ESSA instruction in this case). This will mess up the PSW.
So this never worked and therefore never really triggered.
Looking at the details, we don't even have to perform any validity checks.
1. Bits 52-63 of an entry are stored as 0 by the hardware.
2. We are dealing with absolute addresses but only check for the prefix
starting at address 0. This isn't correct and doesn't make much sense,
cpus could still zap the prefix of other cpus. But as prefix pages
cannot be swapped out without a notifier being called for the affected
VCPU, a zap can never remove a protected prefix.
Reviewed-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'kernel/irq/spurious.c')
0 files changed, 0 insertions, 0 deletions