From: "liyu@WAN" <liyu@ccoss.com.cn>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [Question] How get instruction pointer of user space ???
Date: Wed, 31 Aug 2005 17:59:36 +0800 [thread overview]
Message-ID: <43157F88.60900@ccoss.com.cn> (raw)
Hi everyone:
I am implemnting one ioctl() in one character device.
That need know instruction pointer of user space. I am on i386
platform.
I can sure I am in process context. and enter kernel by system call way.
As I known, in default case, each task have one kernel stack, its length
is THREAD_SIZE(2 pages), and current_thread_info() is at its top. the
struct pt_regs is at bottom of this stack.
so I write the code like here:
pt_regs = ((struct pt_regs *)(THREAD_SIZE + current_thread_info()))+1;
return pt_regs->eip;
but it do not work! even, I get segment fault and kernel Oops at
sometime.
Also, I am sure current_thread_info() return right value of current
user task.
Any idea on here?
thanks
sailor.
next reply other threads:[~2005-08-31 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 9:59 liyu@WAN [this message]
2005-08-31 12:23 ` [Question] How get instruction pointer of user space ??? Gaurav Dhiman
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=43157F88.60900@ccoss.com.cn \
--to=liyu@ccoss.com.cn \
--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