Andreas Kling 4ebff10bde Kernel: Write-only regions should still be mapped as present ...

There is no real "read protection" on x86, so we have no choice but to
map write-only pages simply as "present & read/write".

If we get a read page fault in a non-readable region, that's still a
correctness issue, so we crash the process. It's by no means a complete
protection against invalid reads, since it's trivial to fool the kernel
by first causing a write fault in the same region.

2020-01-20 13:13:03 +01:00

17 KiB

Raw Blame History

View Raw