diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2016-06-13 10:49:04 +0200 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2016-06-20 09:55:20 +0200 |
| commit | 01f719176f28016da1b588f6560a4eef18a98a93 (patch) | |
| tree | 1ce75d8a85c078e46bd23733cf7fc098dc21b8dd /lib/atomic64_test.c | |
| parent | 5b6c963bcef5c3a857e3f8ba84aa9380069fc95f (diff) | |
| download | talos-obmc-linux-01f719176f28016da1b588f6560a4eef18a98a93.tar.gz talos-obmc-linux-01f719176f28016da1b588f6560a4eef18a98a93.zip | |
s390/mm: don't fault everything in read-write in gmap_pte_op_fixup()
Let's not fault in everything in read-write but limit it to read-only
where possible.
When restricting access rights, we already have the required protection
level in our hands. When reading from guest 2 storage (gmap_read_table),
it is obviously PROT_READ. When shadowing a pte, the required protection
level is given via the guest 2 provided pte.
Based on an initial patch by Martin Schwidefsky.
Acked-by: Martin Schwidefsky <schwidefsky@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 'lib/atomic64_test.c')
0 files changed, 0 insertions, 0 deletions
