Thanks, I'll check it out.
On Mon, Oct 29, 2018 at 3:45 PM Steffen Vogel wrote:
> Hi Carter,
>
> On Mon, Oct 29, 2018 at 03:33:02PM +0800, Carter Cheng wrote:
> > Is the /mm directory the correct place to look? It seems to contain
> memory
> > related code but from what little I have read it
Hi Carter,
On Mon, Oct 29, 2018 at 03:33:02PM +0800, Carter Cheng wrote:
> Is the /mm directory the correct place to look? It seems to contain memory
> related code but from what little I have read it seems at a higher level
> building in some cases at least on kmalloc.
Most if the paging/MMU
Is the /mm directory the correct place to look? It seems to contain memory
related code but from what little I have read it seems at a higher level
building in some cases at least on kmalloc. I am just curious about a point
raised by the SVA dissertation(by John Criswell). Another point he does
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
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
Hi,
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
