The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>,
	akpm@osdl.org, davem@davemloft.net, ananth@in.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kprobes: Allow/deny probes on int3/breakpoint instruction?
Date: 31 Mar 2005 13:29:38 +0200
Date: Thu, 31 Mar 2005 13:29:38 +0200	[thread overview]
Message-ID: <20050331112938.GJ24804@muc.de> (raw)
In-Reply-To: <20050331080714.GB31660@in.ibm.com>

> This patch fixes the above problem by doing a proper exit while avoiding
> recursion.
> Any pointers/suggestions on the above issues will be helpful.

Patch is fine for x86-64.

-Andi


      parent reply	other threads:[~2005-03-31 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  8:07 [PATCH] Kprobes: Allow/deny probes on int3/breakpoint instruction? Prasanna S Panchamukhi
2005-03-31  8:17 ` Prasanna S Panchamukhi
2005-03-31  8:43 ` Prasanna S Panchamukhi
2005-03-31 11:29 ` Andi Kleen [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=20050331112938.GJ24804@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ananth@in.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --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