All of lore.kernel.org
 help / color / mirror / Atom feed
From: yzhar <yzhar@varonis.com>
To: linux-kernel@vger.kernel.org
Subject: How to figure READONLY kernel space address/page
Date: Wed, 2 Jul 2008 04:21:21 -0700 (PDT)	[thread overview]
Message-ID: <18235306.post@talk.nabble.com> (raw)


Hi there,

I would like to figure out if a kernel space address is within a READONLY
page (even for kernel usage).
The code is within an LKM, so I guess I'm a bit constraint to exported
kernel methods.
I can see the pgtbl entry holding such information, but could not figure out
how to get pte_t* from a kernel address.

One other thing I'm confused with is "what methods/symbols could I use
within an LKM"? (The LKM is build out of kernel build).
Some articles suggested the /proc/kallsyms searching for the _T_ symbols,
but from my short experience it doesn't correspond.
Could you enlighten this issue? 

Btw,
I'm very new to the Linux kernel.

Thx,
Yzhar

-- 
View this message in context: http://www.nabble.com/How-to-figure-READONLY-kernel-space-address-page-tp18235306p18235306.html
Sent from the linux-kernel mailing list archive at Nabble.com.


                 reply	other threads:[~2008-07-02 11:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=18235306.post@talk.nabble.com \
    --to=yzhar@varonis.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.