From: Peter Zijlstra <peterz@infradead.org>
To: PRINGLE Chris <chris.pringle@miranda.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: kmem_cache_destroy issue with RT12 patch on v3.0.3 (perhaps related to thread 3.0.4 + rt12: deadlock?)
Date: Tue, 06 Sep 2011 13:58:50 +0200 [thread overview]
Message-ID: <1315310330.12533.2.camel@twins> (raw)
In-Reply-To: <FBCF5AA02BB36243866FEDBD9889FC720637233484@uk-ops-exch01>
On Fri, 2011-09-02 at 12:02 +0100, PRINGLE Chris wrote:
> The following code causes the a kernel OOPS at the point where I call
> kmem_cache_destroy:
>
What does that oops look like?
next prev parent reply other threads:[~2011-09-06 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 11:02 kmem_cache_destroy issue with RT12 patch on v3.0.3 (perhaps related to thread 3.0.4 + rt12: deadlock?) PRINGLE Chris
2011-09-06 11:58 ` Peter Zijlstra [this message]
2012-06-28 17:40 ` PRINGLE Chris
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=1315310330.12533.2.camel@twins \
--to=peterz@infradead.org \
--cc=chris.pringle@miranda.com \
--cc=linux-rt-users@vger.kernel.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).