From: Mike Galbraith <bitbucket@online.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 3.[68]-rt: CONFIG_PROVE_LOCKING + CONFIG_DEBUG_FORCE_WEAK_PER_CPU = boot time swap_lock deadlock
Date: Tue, 23 Apr 2013 05:13:11 +0200 [thread overview]
Message-ID: <1366686791.4731.16.camel@marge.simpson.net> (raw)
In-Reply-To: <1366685257.9609.147.camel@gandalf.local.home>
On Mon, 2013-04-22 at 22:47 -0400, Steven Rostedt wrote:
> Yeah, the bug is with the swap_lock not being unique (do a git grep
> swap_lock), and it being weak made that per_cpu swap_lock the same lock
> as the other locks.
>
> Apply my patch and your bug should go away.
Aha, so the bug is certainly dead. I'll test anyway, but you can take
no news as confirmation that it's dead.
-Mike
next prev parent reply other threads:[~2013-04-23 3:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 11:07 3.[68]-rt: CONFIG_PROVE_LOCKING + CONFIG_DEBUG_FORCE_WEAK_PER_CPU = boot time swap_lock deadlock Mike Galbraith
2013-04-23 2:44 ` Steven Rostedt
2013-04-23 2:47 ` Steven Rostedt
2013-04-23 3:13 ` Mike Galbraith [this message]
2013-04-23 16:00 ` Steven Rostedt
2013-04-23 19:06 ` Mike Galbraith
2013-04-24 5:47 ` Mike Galbraith
2013-04-23 3:08 ` Mike Galbraith
2013-04-26 9:16 ` Sebastian Andrzej Siewior
2013-04-26 12:13 ` Steven Rostedt
2013-04-26 13:38 ` Sebastian Andrzej Siewior
2013-04-26 13:52 ` Steven Rostedt
2013-04-26 14:04 ` Sebastian Andrzej Siewior
2013-04-26 14:15 ` Steven Rostedt
2013-04-26 14:49 ` Sebastian Andrzej Siewior
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=1366686791.4731.16.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.