From: Mikado <mikado4vn@gmail.com>
To: openbsd shen <openbsd.shen@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Read /dev/kmem failed
Date: Mon, 27 Mar 2006 00:32:37 +0700 [thread overview]
Message-ID: <4426D035.8050608@gmail.com> (raw)
In-Reply-To: <6ff3e7140603211729s7c64b1f4n@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> struct descriptor_idt {
> unsigned short offset_low, seg_selector;
> unsigned char reserved, flag;
> unsigned short offset_high;
> };
>
> .......
>
> struct descriptor_idt *descriptor;
> .......
>
> fd_kmem = open("/dev/kmem", O_RDWR);
> ptr_idt = get_addr_idt();
> descriptor = (struct descriptor_idt *) malloc(sizeof(struct
> descriptor_idt));
> ......
> readkmem(descriptor, ptr_idt + 8 * x, sizeof(struct descriptor_idt));
>
> ......
>
> void readkmem(void *m, unsigned off, int size)
> {
> int i;
> if (lseek(fd_kmem, off, SEEK_SET) != off) {
> fprintf(stderr, "Error lseek. Are you root? \n");
> exit(-1);
> }
> if ((i = read(fd_kmem, m, size)) != size) {
> fprintf(stderr, "Error read kmem, only read %d bytes\n",i);
> perror("read");
> exit(-1);
> }
> }
>
> unsigned long get_addr_idt(void)
> {
> unsigned char idtr[6];
> unsigned long idt;
> __asm__ volatile ("sidt %0":"=m" (idtr));
> idt = *((unsigned long *) &idtr[2]);
> return (idt);
> }
> ----------------------------------------------------------------------
> When run it, the output is:
>
> Error read kmem, only read 0 bytes
> read: Success
>
>
> I don't know why read error?
finding sys_call_table, system calls' addresses and patching kernel
on-the-fly, isn't it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEJtA1NWc9T2Wr2JcRAt+/AJwMnoR9grdus8ajTjjIJhuNfc8BOQCZAQhI
ESRe1fcd/1tEVD3PRakjkgs=
=H7ni
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-26 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 1:29 Read /dev/kmem failed openbsd shen
2006-03-22 16:04 ` Glynn Clements
2006-03-26 17:32 ` Mikado [this message]
2006-03-26 17:50 ` Steve Graegert
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=4426D035.8050608@gmail.com \
--to=mikado4vn@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=openbsd.shen@gmail.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).