From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MMU related code
Date: Sun, 28 Oct 2018 21:49:06 -0400 [thread overview]
Message-ID: <180249.1540777746@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CALS6=qVfW3dy0uaAm4z+uneh3f75tN7tm_c=E=96miK_HvoSzA@mail.gmail.com>
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: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181028/ad681067/attachment.sig>
next prev parent reply other threads:[~2018-10-29 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 16:08 MMU related code Carter Cheng
2018-10-29 1:49 ` valdis.kletnieks at vt.edu [this message]
2018-10-29 2:44 ` SeyedAlireza Sanaee
2018-10-29 7:33 ` Carter Cheng
2018-10-29 7:45 ` Steffen Vogel
2018-10-29 8:01 ` Carter Cheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=180249.1540777746@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).