From mboxrd@z Thu Jan 1 00:00:00 1970 From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu) Date: Sun, 28 Oct 2018 21:49:06 -0400 Subject: MMU related code In-Reply-To: References: Message-ID: <180249.1540777746@turing-police.cc.vt.edu> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 486 bytes Desc: not available URL: