All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Steven Rostedt <rostedt@goodmis.org>, x86-ml <x86@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>,
	joel@joelfernandes.org
Subject: Re: 4.19-rc1: ./include/linux/rcupdate.h:631 rcu_read_lock() used illegally while idle!
Date: Wed, 5 Sep 2018 05:59:41 -0700	[thread overview]
Message-ID: <20180905125941.GE4225@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180905082254.GA2237@zn.tnic>

On Wed, Sep 05, 2018 at 10:22:54AM +0200, Borislav Petkov wrote:
> On Tue, Sep 04, 2018 at 01:53:21PM -0700, Paul E. McKenney wrote:
> > I must defer to Borislav on this one.  Assuming it has the desired
> > effect, I am good with it.
> 
> It did survive a bunch of reboots (the WARN would fire after boot
> finishes, normally) so I guess we can run with it and see how it works
> out in the next couple of weeks.
> 
> Thanks guys!

Woo-hoo!!!  Thank you for testing this!

							Thanx, Paul


  reply	other threads:[~2018-09-05 12:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01 17:35 4.19-rc1: ./include/linux/rcupdate.h:631 rcu_read_lock() used illegally while idle! Borislav Petkov
2018-09-01 17:54 ` Paul E. McKenney
2018-09-01 22:45   ` Steven Rostedt
2018-09-02  4:16     ` Paul E. McKenney
2018-09-04 20:26       ` Steven Rostedt
2018-09-04 20:53         ` Paul E. McKenney
2018-09-05  8:22           ` Borislav Petkov
2018-09-05 12:59             ` Paul E. McKenney [this message]
2018-09-05 13:07               ` Steven Rostedt
2018-09-05 13:26               ` [PATCH] tracing: Add back in rcu_irq_enter/exit_irqson() for rcuidle tracepoints Steven Rostedt
2018-09-05 15:05                 ` 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=20180905125941.GE4225@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bp@alien8.de \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.