Hi,
A BUGGY MMU may also have some security implications, like flawed protection of one process against another one. MMU may work fine without any performance or functionality issue. But it might reveal one's address space to the others.
I'm not sure if what I have told is true but let me know if it is wrong pls!
Thanks
On Mon, Oct 29, 2018 at 9:50 AM <valdis.kletnieks@xxxxxx> wrote:
On Mon, 29 Oct 2018 00:08:12 +0800, Carter Cheng said:
> Where do I find the code in the kernel related to the MMU and resolving
> memory addresses? I am trying to understand what the implications are if
> code like this has bugs and the impact on the various functions that return
> chunks of memory for use via pointers (either as pages or kmalloc chunks)
> etc.
The results are easy enough to predict even without looking at the code. If your
memory allocations are buggy, you get random memory overlays and corruption,
attempts to access non-mapped physical or virtual memory addresses, and so on.
Basically, all the same sorts of issues beginning C programmers encounter before
they understand pointers.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
