linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Scott Kaplan <sfkaplan@cs.amherst.edu>
To: linux-mm@kvack.org
Subject: Obtaining the kernel's PTEs
Date: Fri, 13 Sep 2002 17:06:59 -0400	[thread overview]
Message-ID: <BDF7B0A2-C75C-11D6-8D39-000393829FA4@cs.amherst.edu> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yet another question...

Assume that I'm not concerned with ZONE_HIGHMEM, and I have a struct page*
.  How would I obtain a pointer to the PTE that maps the corresponding 
virtual page in the kernel's address space to this given page?

In case you're wondering, ``Why does he want that?'':  I want to remove 
access permissions for pages, and I want to include the kernel in that 
denial of permission.  An example of where this matters is when you have a 
page cache page that was allocated by the VFS for read()/write() 
operations on a regular (non-mmaped) file.  Only the kernel has a mapping 
to that page, and I a trap to occur when the kernel tries to use that page.

Must I get the PGD, PMD, and then PTE?  Is there a function that will do 
this nicely for me so that I don't write redundant (and potentially buggy)
  code for this little task?

Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE9glN28eFdWQtoOmgRAof5AJ4tBOxrX6g74RiFezCQfrsooJjwLQCgq0V4
sH16r3mkat6WMtbqx9JcBbk=
=HSwE
-----END PGP SIGNATURE-----

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

             reply	other threads:[~2002-09-13 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 21:06 Scott Kaplan [this message]
2002-09-13 22:10 ` William Lee Irwin III
2002-09-15 21:02   ` Scott Kaplan
2002-09-15 22:44     ` William Lee Irwin III

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=BDF7B0A2-C75C-11D6-8D39-000393829FA4@cs.amherst.edu \
    --to=sfkaplan@cs.amherst.edu \
    --cc=linux-mm@kvack.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