From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: rcu_prempt stalls / lockup
Date: Thu, 3 Apr 2014 17:44:30 -0400 [thread overview]
Message-ID: <20140403214430.GA20249@redhat.com> (raw)
In-Reply-To: <20140403204656.GI4284@linux.vnet.ibm.com>
On Thu, Apr 03, 2014 at 01:46:56PM -0700, Paul E. McKenney wrote:
> So, how about reverting each commit in the RCU series, and then bisecting
> through the reverts? Something like the following:
>
> wherever=linus/master # or substitute whatever point you wish.
> # Create a revert branch for the rcu.2014.02.26a branch
> git checkout -b anti-fixes $wherever
> git revert 5cb5c6e18f822b19bd41a2c0f9930c82b3ec0bc9
> git revert 7a754743185a4b05818e10058fa2fbe4e6969085
> git revert 8857563b819b140aa8c9be920cfe44d5d3f808b7
> git revert add1f0995454374d90c9d6b2c420d2fba3d0a4e3
> git revert ae1670339c95c3ff96ab10582506cf827c5fecc8
> git revert 52e2bb958ac4f9b3c4bdd78606d279852fd72922
> git revert 88c1863066ccfa456797e12c5d8b4631aa1ad0d0
> git revert 0adab9b9aa18d7e90337d43567f1eec3d5401b81
> git revert 41f4abd92a34f9c5110bbb870c04f8854604e28d
> git revert cb1e78cfa267453bb19e7edafd214c03834b664c
> git revert 87de1cfdc55b16b794e245b07322340725149d62
> git revert 3660c2813fb6d0ba48ee44bcbf9feddf7218c11d
> # Create a revert branch for the rt.2014.02.17b branch
> git checkout -b anti-rt $wherever
> git revert f1f399d1281ea339a08469f7e58193624992f620
> git revert ffa83fb565fbc397cbafb4b71fd1cce276d4c3b6
> git revert 2f33b512a5460578f6cf11d7b7867bed53157c7c
> git merge anti-fixes
>
> Then bisect through these reverts.
>
> I am assuming, perhaps naively, that changes under Documentation and
> to torture testing should not be affecting you.
>
> Does this make sense?
I tried reverting every one of those and could still hit it, which
seems to indicate the bug is elsewhere, and rcu is just a victim of it.
I'm going to start trying to revert the lockdep changes, given this seems
to happen after that has warned..
Dave
next prev parent reply other threads:[~2014-04-03 21:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 23:02 rcu_prempt stalls / lockup Dave Jones
2014-03-31 23:22 ` Paul E. McKenney
2014-03-31 23:35 ` Dave Jones
2014-04-01 0:48 ` Paul E. McKenney
2014-04-01 15:08 ` Dave Jones
2014-04-01 15:30 ` Paul E. McKenney
2014-04-01 17:22 ` Dave Jones
2014-04-01 17:55 ` Paul E. McKenney
2014-04-01 18:04 ` Dave Jones
2014-04-01 18:32 ` Paul E. McKenney
2014-04-01 22:16 ` Dave Jones
2014-04-01 23:18 ` Paul E. McKenney
2014-04-01 23:31 ` Dave Jones
2014-04-01 23:57 ` Paul E. McKenney
2014-04-02 0:07 ` Dave Jones
2014-04-02 16:20 ` Paul E. McKenney
2014-04-02 16:23 ` Dave Jones
2014-04-02 22:48 ` Dave Jones
2014-04-03 20:01 ` Dave Jones
2014-04-03 20:46 ` Paul E. McKenney
2014-04-03 21:44 ` Dave Jones [this message]
2014-04-03 22:37 ` Dave Jones
2014-04-04 17:06 ` Paul E. McKenney
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=20140403214430.GA20249@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).