From: Dan Malek <dan@embeddededge.com>
To: ming lei <mlei30@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: double kernel page table entry for the same physical page?!
Date: Wed, 13 Jul 2005 15:36:13 -0700 [thread overview]
Message-ID: <17068cbdcbb1e2de531d33eb07f768e5@embeddededge.com> (raw)
In-Reply-To: <20050713214802.68288.qmail@web61016.mail.yahoo.com>
On Jul 13, 2005, at 2:48 PM, ming lei wrote:
> Why linux kernel does such thing and no one consider
> it's a problem?
Because we don't write software that accesses the memory
from both of those locations, unless it is very intentional
and necessary. If you are just fishing for ways software
_could_ do bad things, there are tons of them. It's our
job to write it so it doesn't :-)
Thanks.
-- Dan
next prev parent reply other threads:[~2005-07-13 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 20:10 double kernel page table entry for the same physical page?! ming lei
2005-07-13 21:27 ` Dan Malek
2005-07-13 21:48 ` ming lei
2005-07-13 22:36 ` Dan Malek [this message]
2005-07-14 1:57 ` ming lei
2005-07-14 7:15 ` Pantelis Antoniou
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=17068cbdcbb1e2de531d33eb07f768e5@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mlei30@yahoo.com \
/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).