From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: akpm@osdl.org, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppc64: kprobes breaks BUG() handling
Date: Mon, 10 Jan 2005 18:08:26 +0530 [thread overview]
Message-ID: <20050110123826.GA10736@in.ibm.com> (raw)
In-Reply-To: <20050110111937.GN14239@krispykreme.ozlabs.ibm.com>
On Mon, Jan 10, 2005 at 10:19:37PM +1100, Anton Blanchard wrote:
>
> Hi,
>
> I was running some tests and noticed BUG() handling wasnt working as
> expected. The kprobes code has some code to check for breakpoint
> removal races and only checks for one opcode. It turns out there are
> many forms of the breakpoint instruction, comparing against one is not
> good enough.
Ah yes! I see that BUG() uses twi. I will try and send out a patch for
this soon.
Thanks,
Ananth
next prev parent reply other threads:[~2005-01-10 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 11:19 [PATCH] ppc64: kprobes breaks BUG() handling Anton Blanchard
2005-01-10 12:38 ` Ananth N Mavinakayanahalli [this message]
2005-01-12 11:30 ` 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=20050110123826.GA10736@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/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 NNTP newsgroup(s).