public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 24 Apr 2013 07:47:24 +0200	[thread overview]
Message-ID: <1366782444.5921.4.camel@marge.simpson.net> (raw)
In-Reply-To: <1366732855.9609.158.camel@gandalf.local.home>

On Tue, 2013-04-23 at 12:00 -0400, Steven Rostedt wrote: 
> On Tue, 2013-04-23 at 05:13 +0200, Mike Galbraith wrote:
> > 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.
> > 
> 
> Actually, I would feel more comfortable if I heard news that confirms
> its dead ;-)
> 
> /me hopes to hear "It's dead Jim".

It's-dead-Jim-by: Mike Galbraith <bitbucket@online.de>

For 3.6-rt tested, I added the hunk below, which isn't in 3.8-rt..

@@ -850,7 +850,7 @@ EXPORT_SYMBOL(pagevec_lookup_tag);
 static int __init swap_init_locks(void)
 {
 	local_irq_lock_init(rotate_lock);
-	local_irq_lock_init(swap_lock);
+	local_irq_lock_init(swapvec_lock);
 	return 1;
 }
 early_initcall(swap_init_locks);

..and build fix stolen from 3.8-rt.

From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: gpu/i915: don't open code these things

Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 drivers/gpu/drm/i915/i915_gem.c |   10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -90,7 +90,6 @@ i915_gem_wait_for_error(struct drm_devic
 {
 	struct drm_i915_private *dev_priv = dev->dev_private;
 	struct completion *x = &dev_priv->error_completion;
-	unsigned long flags;
 	int ret;
 
 	if (!atomic_read(&dev_priv->mm.wedged))
@@ -115,9 +114,7 @@ i915_gem_wait_for_error(struct drm_devic
 		 * end up waiting upon a subsequent completion event that
 		 * will never happen.
 		 */
-		spin_lock_irqsave(&x->wait.lock, flags);
-		x->done++;
-		spin_unlock_irqrestore(&x->wait.lock, flags);
+		complete(x);
 	}
 	return 0;
 }
@@ -1884,12 +1881,9 @@ i915_gem_check_wedge(struct drm_i915_pri
 	if (atomic_read(&dev_priv->mm.wedged)) {
 		struct completion *x = &dev_priv->error_completion;
 		bool recovery_complete;
-		unsigned long flags;
 
 		/* Give the error handler a chance to run. */
-		spin_lock_irqsave(&x->wait.lock, flags);
-		recovery_complete = x->done > 0;
-		spin_unlock_irqrestore(&x->wait.lock, flags);
+		recovery_complete = completion_done(x);
 
 		/* Non-interruptible callers can't handle -EAGAIN, hence return
 		 * -EIO unconditionally for these. */



  parent reply	other threads:[~2013-04-24  5:47 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
2013-04-23 16:00       ` Steven Rostedt
2013-04-23 19:06         ` Mike Galbraith
2013-04-24  5:47         ` Mike Galbraith [this message]
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=1366782444.5921.4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox