From: "Jun Koi" <junkoi2004@gmail.com>
To: Keshavamurthy@bambi.jf.intel.com,
"Anil S" <anil.s.keshavamurthy@intel.com>
Cc: prasanna@in.ibm.com, jkenisto@us.ibm.com, hien@us.ibm.com,
systemtap@sources.redhat.com
Subject: Re: [PATCH] kprobes patch
Date: Sat, 28 Oct 2006 01:21:00 -0000 [thread overview]
Message-ID: <fdaac4d50610271821v41ee36f6r6bb0265804bc7922@mail.gmail.com> (raw)
In-Reply-To: <20061027205027.GA10018@bambi.jf.intel.com>
Hi Keshavanmurthy,
On 10/28/06, Keshavamurthy@bambi.jf.intel.com
<Keshavamurthy@bambi.jf.intel.com> wrote:
> On Sat, Oct 28, 2006 at 03:58:18AM +0900, Jun Koi wrote:
> > Hello,
> >
> > I am not sure if this is a right place to send patch for kprobes, but
> > here it is. This patch moves the reset command of kprobe instance
> > into the loop. (against 2.6.18)
>
> Hi jun,
> Yes, you have sent it to the right place. thanks.
> BTW, is is helpful to know what problem did you encounter due to which
> you had come up with this patch. Or did you catch this bug by just code review?
>
I had no problem at al. You are right, the patch is a result of
reviewing the code.
Best,
Jun
> >
> > Signed-off-by: Jun Koi <junkoi2004@gmail.com>
> >
> >
> > --- a/kernel/kprobes.c 2006-09-20 12:42:06.000000000 +0900
> > +++ b/kernel/kprobes.c 2006-10-28 03:52:27.000000000 +0900
> > @@ -204,8 +204,8 @@ static int __kprobes aggr_pre_handler(st
> > set_kprobe_instance(kp);
> > if (kp->pre_handler(kp, regs))
> > return 1;
> > + reset_kprobe_instance();
> > }
> > - reset_kprobe_instance();
> > }
> > return 0;
> > }
>
next prev parent reply other threads:[~2006-10-28 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 18:58 Jun Koi
2006-10-27 20:45 ` Keshavamurthy, Anil S
2006-10-28 1:21 ` Jun Koi [this message]
2006-10-29 18:22 ` Vara Prasad
2006-10-30 18:45 ` Keshavamurthy, Anil S
2006-10-30 18:53 ` Keshavamurthy, Anil S
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=fdaac4d50610271821v41ee36f6r6bb0265804bc7922@mail.gmail.com \
--to=junkoi2004@gmail.com \
--cc=Keshavamurthy@bambi.jf.intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hien@us.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=prasanna@in.ibm.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).