From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: karim@opersys.com
Cc: Richard J Moore <richardj_moore@uk.ibm.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
"Frank Ch. Eigler" <fche@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
SystemTAP <systemtap@sources.redhat.com>,
Satoshi Oshima <soshima@redhat.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Tom Zanussi <zanussi@us.ibm.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
William Cohen <wcohen@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Does this work? "dcprobes" an x86-hack simple djprobes-equivalent?
Date: Thu, 28 Sep 2006 11:30:32 +0900 [thread overview]
Message-ID: <451B33C8.4080107@hitachi.com> (raw)
In-Reply-To: <45163D3D.4010108@opersys.com>
Hi Karim,
Thank you for new idea.
I discussed your proposal deeply with my coworkers.
I think your approach has following advantages/disadvantages/problem;
<advantages>
(a) Able to be inserted into the target address of the branch.
(b) So, binary analysis tool becomes simple.
<disadvantages>
(c) Implementation is much complicated.
(d) Highly depend on the x86 arch.
(e) Bigger overhead than djprobe.
(f) There will be side effect(*)
<problem>
(g) User applications can modify LDT. (ex. wine)
I think the dcprobe will work, but, unfortunately, it has
an vulnerability by the problem (g).
(*) In the following code:
---
a=0
do {
...
a++;
}while (a <= 100)
---
In case of inserting dcprobe at the 1st line (a=0),
it will replace 2nd (or more) instructions.
In this case, the fix up routine (based on int3)
will be invoked one hundred times.
Thanks,
--
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2006-09-28 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 8:09 Does this work? "dcprobes" an x86-hack simple djprobes-equivalent? Karim Yaghmour
2006-09-25 4:46 ` Karim Yaghmour
2006-09-28 2:30 ` Masami Hiramatsu [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=451B33C8.4080107@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=soshima@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.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