From: Catalin Patulea <cat@vv.carleton.ca>
To: linux-kernel@vger.kernel.org
Subject: Reading kmem
Date: Sun, 17 Apr 2005 15:23:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0504171434180.4037@vv.carleton.ca> (raw)
Hello,
I'm having trouble reading from /dev/kmem in Linux 2.4.22 and 2.4.25. I
have written some code available at
http://vv.carleton.ca/~cat/misc/readidt.c. The behavior on both kernel
versions is the following:
# ./readidt
idt: 0xffffe000 + 0x07ff
pointer at 0x00000000ffffe400
read: 0
As read returns 0, it seems as if it's reading past the end of file.
However, the IDT must be present in the kernel's virtual memory. Also,
looking at 2.4.20's read_kmem() (drivers/char/mem.c:215), I don't see how
the function could return 0 unless count was 0.
It would be great if follow-ups could be CC'ed to my e-mail address.
Thank you very much for your time,
Catalin
-----------------------------------------
Catalin Patulea VV Volunteer 2002,3
http://vv.carleton.ca/~cat/ VV HI 2004
cat@vv.carleton.ca
reply other threads:[~2005-04-17 19:27 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=Pine.LNX.4.60.0504171434180.4037@vv.carleton.ca \
--to=cat@vv.carleton.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®