public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: hung tasks in 3.18.0-rc1-00221-gc3351df
Date: Tue, 28 Oct 2014 13:22:52 -0700	[thread overview]
Message-ID: <20141028202251.GZ5718@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1410282147310.19428@adalberg.ut.ee>

On Tue, Oct 28, 2014 at 09:48:21PM +0200, Meelis Roos wrote:
> > > > rcu: Make rcu_barrier() understand about missing rcuo kthreads
> > > 
> > > I can not trigger the previous problem at will so my testing is not very 
> > > useful. I tested the previous patch that you sent but the problem did 
> > > not trigger, and yesterday applied this one and it still does not 
> > > trigger, but I an using remote sessions only for now (no desktop).
> > > 
> > > At least it's not clearly broken :)
> > 
> > A couple of other people had more reproducible test setups and confirmed
> > that it fixed them.
> > 
> > But yes, there are no doubt other RCU bugs waiting to be found.  ;-)
> 
> I reproduced the problem on Thinkpad T400 with Core2Duo and Chromium 
> startup failing, and your patch fixes that.
> 
> Tested-by: Meelis Roos <mroos@linux.ee>

Got it, thank you!!!

							Thanx, Paul


      reply	other threads:[~2014-10-28 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 13:21 hung tasks in 3.18.0-rc1-00221-gc3351df Meelis Roos
2014-10-24  0:18 ` Paul E. McKenney
2014-10-24  7:58   ` Meelis Roos
2014-10-24 14:55     ` Paul E. McKenney
2014-10-27 17:44       ` Paul E. McKenney
2014-10-28  8:16         ` Meelis Roos
2014-10-28 12:49           ` Paul E. McKenney
2014-10-28 19:48             ` Meelis Roos
2014-10-28 20:22               ` Paul E. McKenney [this message]

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=20141028202251.GZ5718@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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