From: Satoshi Oshima <soshima@redhat.com>
To: Andi Kleen <ak@suse.de>, Richard J Moore <richardj_moore@uk.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
"Hideo AOKI@redhat" <haoki@redhat.com>,
Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>,
Jim Keniston <jkenisto@us.ibm.com>,
linux-kernel@vger.kernel.org,
Ananth N Mavinakayanahalli <mananth@in.ibm.com>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
sugita <sugita@sdl.hitachi.co.jp>,
systemtap@sources.redhat.com, systemtap-owner@sourceware.org
Subject: Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64
Date: Fri, 19 May 2006 10:13:22 -0400 [thread overview]
Message-ID: <446DD282.5080402@redhat.com> (raw)
In-Reply-To: <200605191333.11930.ak@suse.de>
Andi Kleen wrote:
> On Friday 19 May 2006 10:29, Richard J Moore wrote:
>> Is there any possibility of a inducing a page fault when checking the
>> second byte?
>
> AFAIK instr is in the out of line instruction copy. Kernel would need
> to be pretty broken already if that page faulted.
There is no possibility that copied instruction step over
a page boundary. Instruction slot is in the page that
is allocated in get_insn_slot(). And get_insn_slot()
acquires the page by module_alloc(), and divides into
slots.
Satoshi Oshima
prev parent reply other threads:[~2006-05-19 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 21:32 [PATCH] kprobes: bad manupilation of 2 byte opcode on x86_64 Satoshi Oshima
2006-05-19 8:29 ` [PATCH] kprobes: bad manipulation " Richard J Moore
2006-05-19 11:33 ` Andi Kleen
2006-05-19 14:13 ` Satoshi Oshima [this message]
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=446DD282.5080402@redhat.com \
--to=soshima@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=haoki@redhat.com \
--cc=hiramatu@sdl.hitachi.co.jp \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mananth@in.ibm.com \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=sugita@sdl.hitachi.co.jp \
--cc=systemtap-owner@sourceware.org \
--cc=systemtap@sources.redhat.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 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.