| commit | 57d0a39d98b0d0e4712e736084667bcb5aed3474 | |
| author | David Gibson <david@gibson.dropbear.id.au> | |
| Tue, 12 Mar 2013 00:31:41 +0000 (12 00:31 +0000) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Fri, 22 Mar 2013 14:28:52 +0000 (22 15:28 +0100) | ||
| tree | 9512326aec8d61db8f6acc37f57503b3767384f1 | treesnapshot (tar.gz zip) |
| parent | e01b444523e2b0c663b42b3e8f44ef48a6153051 | commitdiff |
mmu-hash64: Factor SLB N bit into permissions bits
BEHAVIOUR CHANGE
Currently, for 64-bit hash mmu, the execute protection bit placed into the
qemu tlb is based only on the N (No execute) bit from the PTE. However,
No Execute can also be set at the segment level. We do check this on
execute faults, but this still means we could incorrectly allow execution
of code from a No Execute segment, if a prior read or write fault caused
the page to be loaded into the qemu tlb with PROT_EXEC set.
To correct this, we (re-)check the segment level no execute permission when
generating the protection bits for the qemu tlb.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
BEHAVIOUR CHANGE
Currently, for 64-bit hash mmu, the execute protection bit placed into the
qemu tlb is based only on the N (No execute) bit from the PTE. However,
No Execute can also be set at the segment level. We do check this on
execute faults, but this still means we could incorrectly allow execution
of code from a No Execute segment, if a prior read or write fault caused
the page to be loaded into the qemu tlb with PROT_EXEC set.
To correct this, we (re-)check the segment level no execute permission when
generating the protection bits for the qemu tlb.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
| target-ppc/mmu-hash64.c | diffblobblamehistory |