From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Jones <davej@redhat.com>, Jason Low <jason.low2@hp.com>,
Peter Zijlstra <peterz@infradead.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
"Michael L. Semon" <mlsemon35@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: 3.14.0+/x86: lockdep and mutexes not getting along
Date: Thu, 10 Apr 2014 20:48:16 -0700 [thread overview]
Message-ID: <20140411034816.GB4496@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140410232652.GA24658@redhat.com>
On Thu, Apr 10, 2014 at 07:26:52PM -0400, Dave Jones wrote:
> On Thu, Apr 10, 2014 at 10:14:44AM -0700, Jason Low wrote:
> > On Thu, 2014-04-10 at 11:18 +0200, Peter Zijlstra wrote:
> > > On Wed, Apr 09, 2014 at 10:42:59PM -0700, Jason Low wrote:
> > > > As a starting point, would either of you like to test the following
> > > > patch to see if it fixes the issue? This patch essentially generates the
> > > > same code as in older kernels in the debug case. This applies on top of
> > > > kernels with both commits 6f008e72cd11 and 1d8fe7dc8078.
> > >
> > >
> > > So I managed to reproduce, and the below makes it go away. I just don't
> > > understand why though. will stare more.
> >
> > So one thing I noticed that is different in the current code is that in
> > debug_mutex_unlock(), there is is a possibility that it does not unlock
> > the mutex (when !debug_locks). May be interesting to try out this
> > patch too:
>
> I've been seeing lockups this last week or two too, that manifested by
> RCU spewing stall messages, and the box being totally unresponsive.
> This patch seems to cure that for me, which I'm sure will make Paul
> happy to hear.
Whew!!! ;-)
Thanx, Paul
next prev parent reply other threads:[~2014-04-11 3:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 5:12 3.14.0+/x86: lockdep and mutexes not getting along Michael L. Semon
2014-04-09 12:19 ` Kirill A. Shutemov
2014-04-10 5:42 ` Jason Low
2014-04-10 8:14 ` Peter Zijlstra
2014-04-10 9:15 ` Kirill A. Shutemov
2014-04-10 11:42 ` Peter Zijlstra
2014-04-10 9:18 ` Peter Zijlstra
2014-04-10 14:15 ` Peter Zijlstra
2014-04-11 13:59 ` Valdis.Kletnieks
2014-04-14 7:22 ` [tip:core/urgent] locking/mutex: Fix debug_mutexes tip-bot for Peter Zijlstra
2014-04-10 17:14 ` 3.14.0+/x86: lockdep and mutexes not getting along Jason Low
2014-04-10 17:28 ` Peter Zijlstra
2014-04-10 19:04 ` Jason Low
2014-04-10 23:26 ` Dave Jones
2014-04-10 23:30 ` Dave Jones
2014-04-11 3:48 ` Paul E. McKenney [this message]
2014-04-11 13:41 ` Michael L. Semon
2014-04-10 8:12 ` Peter Zijlstra
2014-04-10 8:13 ` Peter Zijlstra
2014-04-10 14:29 ` cred_guard_mutex vs seq_file::lock [was: Re: 3.14.0+/x86: lockdep and mutexes not getting along] Peter Zijlstra
2014-04-11 14:50 ` David Howells
2014-04-11 15:07 ` Al Viro
2014-07-30 22:31 ` Kirill A. Shutemov
2014-07-30 23:03 ` Kirill A. Shutemov
2014-07-31 7:26 ` Cyrill Gorcunov
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=20140411034816.GB4496@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=jason.low2@hp.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mlsemon35@gmail.com \
--cc=peterz@infradead.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).