Hi, For kernel protection purposes I want to make kernel read-only memory pages also read-only in stage 2 so that if malicious code in the kernel tries to modify read-only memory by first making it writable in stage 1 that then a read-only stage 2 page table entry will catch this.
I want to do this for arm64. How to do this? Where is the 2nd stage table constructed? What kind of exception can I expect when the kernel writes to data via a stage 1 access where writes are allowed followed by a stage 2 where writes are not allowed? Thanks! Regards, Jan -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/CAD9j0toG2Cq3T58xEzDOzHbSpa3fqddcGsLevN54%3DZHH7aWkug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
