From: "David S. Miller" <davem@davemloft.net>
To: ananth@in.ibm.com
Cc: wcohen@redhat.com, systemtap@sources.redhat.com, akpm@osdl.org,
prasanna@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: kprobe_handler should check pre_handler function
Date: Mon, 28 Mar 2005 18:54:08 -0800 [thread overview]
Message-ID: <20050328185408.4b0e215c.davem@davemloft.net> (raw)
In-Reply-To: <20050329023408.GA4847@in.ibm.com>
On Mon, 28 Mar 2005 21:34:08 -0500
Ananth N Mavinakayanahalli <ananth@in.ibm.com> wrote:
> You are right. The check for pre_handler is needed and here is a patch
> against 2.6.12-rc1-mm3 that does this.
The sparc64 part looks just fine.
next prev parent reply other threads:[~2005-03-29 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <424872C8.6080207@redhat.com>
2005-03-29 2:34 ` kprobe_handler should check pre_handler function Ananth N Mavinakayanahalli
2005-03-29 2:54 ` David S. Miller [this message]
2005-03-29 19:18 ` William Cohen
2005-03-29 23:59 ` Ananth N Mavinakayanahalli
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=20050328185408.4b0e215c.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@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