From: Paul Mackerras <paulus@samba.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Hitting WARN_ON in hw_breakpoint code
Date: Thu, 24 Jun 2010 09:53:09 +1000 [thread overview]
Message-ID: <20100623235309.GA17441@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <20100623174918.GH5242@nowhere>
On Wed, Jun 23, 2010 at 07:49:20PM +0200, Frederic Weisbecker wrote:
> Indeed. I'm suprised I've never seen this problem before while the
> bug is quite obvious.
>
> Anyway I'm cooking a fix, thanks for this report!
If you haven't been seeing it on x86, I think I'll look a bit closer.
I would have thought that the perf_event would have a reference to the
context, so the context shouldn't have gone away while the perf_event
still exists. It may be something we're doing differently on ppc64.
Paul.
next prev parent reply other threads:[~2010-06-23 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 12:57 Hitting WARN_ON in hw_breakpoint code Paul Mackerras
2010-06-23 17:49 ` Frederic Weisbecker
2010-06-23 23:53 ` Paul Mackerras [this message]
2010-06-24 6:32 ` Frederic Weisbecker
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=20100623235309.GA17441@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.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