From: Masami Hiramatsu <mhiramat@redhat.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: ananth@in.ibm.com, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
systemtap-ml <systemtap@sources.redhat.com>,
kvm@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH -tip 4/6 V4.1] x86: kprobes checks safeness of insertion address.
Date: Fri, 03 Apr 2009 15:20:06 -0400 [thread overview]
Message-ID: <49D66166.9040002@redhat.com> (raw)
In-Reply-To: <1238779686.3568.18.camel@dyn9047018139.beaverton.ibm.com>
Jim Keniston wrote:
> On Fri, 2009-04-03 at 12:02 -0400, Masami Hiramatsu wrote:
>> Ensure safeness of inserting kprobes by checking whether the specified
>> address is at the first byte of a instruction. This is done by decoding
>> probed function from its head to the probe point.
>>
>> changes from v4:
>> - change a comment according to Ananth's suggestion.
>>
>> Signed-off-by: Masami Hiramatsu <mhiramat@redhat.com>
>> Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
>> Cc: Jim Keniston <jkenisto@us.ibm.com>
>> Cc: Ingo Molnar <mingo@elte.hu>
>> ---
>>
>> arch/x86/kernel/kprobes.c | 51 +++++++++++++++++++++++++++++++++++++++++++++
>> 1 files changed, 51 insertions(+), 0 deletions(-)
>>
>>
>> diff --git a/arch/x86/kernel/kprobes.c b/arch/x86/kernel/kprobes.c
> ...
>> +/* Recover original instruction */
>
> /* Recover the probed instruction at addr for further analysis. */
> See below.
Sure.
>
>> +static int recover_probed_instruction(kprobe_opcode_t *buf, unsigned long addr)
>> +{
>> + struct kprobe *kp;
>> + kp = get_kprobe((void *)addr);
>> + if (!kp)
>> + return -EINVAL;
>> +
>> + /* Don't use p->ainsn.insn; which will be modified by fix_riprel */
>
> fix_riprel doesn't affect the instruction's length, which is what
> concerns this patch. But we want this function to be useful for
> unforeseen uses as well, so I like the code you have. Just consider the
> suggested comment changes.
>
> /*
> * Don't use p->ainsn.insn, which could be modified -- e.g.,
> * by fix_riprel().
> */
Thanks, I'll update comments then!
>
>> + memcpy(buf, kp->addr, MAX_INSN_SIZE * sizeof(kprobe_opcode_t));
>> + buf[0] = kp->opcode;
>> + return 0;
>> +}
>
> Jim Keniston
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: ananth@in.ibm.com, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
systemtap-ml <systemtap@sources.redhat.com>,
kvm@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH -tip 4/6 V4.1] x86: kprobes checks safeness of insertion address.
Date: Fri, 03 Apr 2009 15:20:06 -0400 [thread overview]
Message-ID: <49D66166.9040002@redhat.com> (raw)
In-Reply-To: <1238779686.3568.18.camel@dyn9047018139.beaverton.ibm.com>
Jim Keniston wrote:
> On Fri, 2009-04-03 at 12:02 -0400, Masami Hiramatsu wrote:
>> Ensure safeness of inserting kprobes by checking whether the specified
>> address is at the first byte of a instruction. This is done by decoding
>> probed function from its head to the probe point.
>>
>> changes from v4:
>> - change a comment according to Ananth's suggestion.
>>
>> Signed-off-by: Masami Hiramatsu <mhiramat@redhat.com>
>> Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
>> Cc: Jim Keniston <jkenisto@us.ibm.com>
>> Cc: Ingo Molnar <mingo@elte.hu>
>> ---
>>
>> arch/x86/kernel/kprobes.c | 51 +++++++++++++++++++++++++++++++++++++++++++++
>> 1 files changed, 51 insertions(+), 0 deletions(-)
>>
>>
>> diff --git a/arch/x86/kernel/kprobes.c b/arch/x86/kernel/kprobes.c
> ...
>> +/* Recover original instruction */
>
> /* Recover the probed instruction at addr for further analysis. */
> See below.
Sure.
>
>> +static int recover_probed_instruction(kprobe_opcode_t *buf, unsigned long addr)
>> +{
>> + struct kprobe *kp;
>> + kp = get_kprobe((void *)addr);
>> + if (!kp)
>> + return -EINVAL;
>> +
>> + /* Don't use p->ainsn.insn; which will be modified by fix_riprel */
>
> fix_riprel doesn't affect the instruction's length, which is what
> concerns this patch. But we want this function to be useful for
> unforeseen uses as well, so I like the code you have. Just consider the
> suggested comment changes.
>
> /*
> * Don't use p->ainsn.insn, which could be modified -- e.g.,
> * by fix_riprel().
> */
Thanks, I'll update comments then!
>
>> + memcpy(buf, kp->addr, MAX_INSN_SIZE * sizeof(kprobe_opcode_t));
>> + buf[0] = kp->opcode;
>> + return 0;
>> +}
>
> Jim Keniston
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-04-03 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 17:24 [PATCH -tip 4/6 V4] x86: kprobes checks safeness of insertion address Masami Hiramatsu
2009-04-03 5:18 ` Ananth N Mavinakayanahalli
2009-04-03 16:02 ` [PATCH -tip 4/6 V4.1] " Masami Hiramatsu
2009-04-03 17:28 ` Jim Keniston
2009-04-03 17:28 ` Jim Keniston
2009-04-03 19:20 ` Masami Hiramatsu [this message]
2009-04-03 19:20 ` Masami Hiramatsu
2009-04-03 21:21 ` [PATCH -tip 4/6 V4.2] " Masami Hiramatsu
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=49D66166.9040002@redhat.com \
--to=mhiramat@redhat.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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.