public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@canonical.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Jason Low <jason.low2@hp.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Sasha Levin <sasha.levin@oracle.com>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>
Subject: Re: softlockups in multi_cpu_stop
Date: Sat, 7 Mar 2015 09:55:26 +0800	[thread overview]
Message-ID: <20150307095526.5ffb1bf0@tom-ThinkPad-T410> (raw)
In-Reply-To: <1425680137.19505.63.camel@stgolabs.net>

On Fri, 06 Mar 2015 14:15:37 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:

> On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> > In owner_running() there are 2 conditions that would make it return
> > false: if the owner changed or if the owner is not running. However,
> > that patch continues spinning if there is a "new owner" but it does not
> > take into account that we may want to stop spinning if the owner is not
> > running (due to getting rescheduled).
> 
> So you're rationale is that we're missing this need_resched:
> 
> 	while (owner_running(sem, owner)) {
> 		/* abort spinning when need_resched */
> 		if (need_resched()) {
> 			rcu_read_unlock();
> 			return false;
> 		}
> 	}
> 
> Because the owner_running() would return false, right? Yeah that makes
> sense, as missing a resched is a bug, as opposed to our heuristics being
> so painfully off.
> 
> Sasha, Ming (Cc'ed), does this address the issues you guys are seeing?

For the xfstest lockup, what matters is that the owner isn't running, since
the following simple change does fix the issue:

diff --git a/kernel/locking/rwsem-xadd.c b/kernel/locking/rwsem-xadd.c
index 06e2214..5e08705 100644
--- a/kernel/locking/rwsem-xadd.c
+++ b/kernel/locking/rwsem-xadd.c
@@ -358,8 +358,9 @@ bool rwsem_spin_on_owner(struct rw_semaphore *sem, struct task_struct *owner)
 	}
 	rcu_read_unlock();
 
-	if (READ_ONCE(sem->owner))
-		return true; /* new owner, continue spinning */
+	owner = READ_ONCE(sem->owner);
+	if (owner && owner->on_cpu)
+		return true;
 
 	/*
 	 * When the owner is not set, the lock could be free or


Thanks,
Ming Lei

  reply	other threads:[~2015-03-07  1:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  7:45 sched: softlockups in multi_cpu_stop Sasha Levin
     [not found] ` <CAMiJ5CVWvUhGK=MWYB_CTNs901p=jsT4i5gkWTaHih7qdQdkFQ@mail.gmail.com>
2015-03-04  5:44   ` Rafael David Tinoco
2015-03-06 11:27 ` Sasha Levin
2015-03-06 12:32   ` Ingo Molnar
2015-03-06 14:34     ` Rafael David Tinoco
2015-03-06 14:45       ` Sasha Levin
2015-03-06 15:46         ` Sasha Levin
2015-03-06 17:19     ` Davidlohr Bueso
2015-03-06 18:02       ` Sasha Levin
2015-03-06 21:59         ` Sasha Levin
2015-03-06 18:57       ` Jason Low
2015-03-06 19:05         ` Linus Torvalds
2015-03-06 19:20           ` Davidlohr Bueso
2015-03-06 19:32             ` Linus Torvalds
2015-03-06 19:45               ` Davidlohr Bueso
2015-03-06 19:55               ` Davidlohr Bueso
2015-03-06 20:00                 ` Davidlohr Bueso
2015-03-06 21:42                 ` Linus Torvalds
2015-03-06 19:29           ` Jason Low
2015-03-06 21:12             ` Jason Low
2015-03-06 21:24               ` Linus Torvalds
2015-03-07  1:53                 ` Jason Low
2015-03-06 22:15               ` Davidlohr Bueso
2015-03-07  1:55                 ` Ming Lei [this message]
2015-03-07  2:07                   ` Davidlohr Bueso
2015-03-07  2:10                     ` Ming Lei
2015-03-07  2:26                       ` Davidlohr Bueso
2015-03-07  2:29                         ` Davidlohr Bueso
2015-03-07  2:55                           ` Ming Lei
2015-03-07  3:10                             ` Davidlohr Bueso
2015-03-07  3:19                               ` Ming Lei
2015-03-07  3:41                                 ` Davidlohr Bueso
2015-03-07  2:56                       ` Jason Low
2015-03-07  3:08                         ` Ming Lei
2015-03-07  3:10                           ` Davidlohr Bueso
2015-03-07  3:17                           ` Jason Low
2015-03-07  3:39                             ` Ming Lei
2015-03-07  3:53                               ` Jason Low
2015-03-07  1:58                 ` Jason Low
2015-03-07  4:31               ` Jason Low
2015-03-07  4:44                 ` Davidlohr Bueso
2015-03-07  6:45                   ` Jason Low
2015-03-07  5:54                 ` Ming Lei
2015-03-07  6:57                   ` Jason Low

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=20150307095526.5ffb1bf0@tom-ThinkPad-T410 \
    --to=ming.lei@canonical.com \
    --cc=dave@stgolabs.net \
    --cc=davej@codemonkey.org.uk \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.com \
    --cc=torvalds@linux-foundation.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