From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
dhowells@redhat.com, edumazet@google.com, fweisbec@gmail.com,
oleg@redhat.com, joel@joelfernandes.org,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH tip/core/rcu 3/3] srcu: Make early-boot call_srcu() reuse workqueue lists
Date: Thu, 30 Aug 2018 14:36:17 -0400 [thread overview]
Message-ID: <20180830143617.2fb85e23@gandalf.local.home> (raw)
In-Reply-To: <20180830173742.GA17677@linux.vnet.ibm.com>
On Thu, 30 Aug 2018 10:37:42 -0700
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> > > But still triggered the following:
> > >
> > > WARNING: CPU: 0 PID: 0 at /work/git/linux-trace.git/kernel/rcu/srcutree.c:242 check_init_srcu_struct+0x85/0x90
> >
> > Gah!!! I needed to have removed that WARN_ON_ONCE(), didn't I?
> > In fact, I should have removed that once I started using workqueues,
> > quite some time back.
>
> As in the below patch.
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> index 75571ff09c62..a8846ed7f352 100644
> --- a/kernel/rcu/srcutree.c
> +++ b/kernel/rcu/srcutree.c
> @@ -239,7 +239,6 @@ static void check_init_srcu_struct(struct srcu_struct *sp)
> {
> unsigned long flags;
>
> - WARN_ON_ONCE(rcu_scheduler_active == RCU_SCHEDULER_INIT);
Well it boots without warning ;-)
Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> /* The smp_load_acquire() pairs with the smp_store_release(). */
> if (!rcu_seq_state(smp_load_acquire(&sp->srcu_gp_seq_needed))) /*^^^*/
> return; /* Already initialized. */
next prev parent reply other threads:[~2018-08-30 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 21:20 [PATCH tip/core/rcu 0/3] SRCU updates for v4.20/v5.0 Paul E. McKenney
2018-08-29 21:23 ` [PATCH tip/core/rcu 1/3] srcu: Make call_srcu() available during very early boot Paul E. McKenney
2018-08-30 18:24 ` [PATCH tip/core/rcu v2 " Paul E. McKenney
2018-08-29 21:23 ` [PATCH tip/core/rcu 2/3] rcutorture: Test early boot call_srcu() Paul E. McKenney
2018-08-29 21:23 ` [PATCH tip/core/rcu 3/3] srcu: Make early-boot call_srcu() reuse workqueue lists Paul E. McKenney
2018-08-30 1:56 ` Steven Rostedt
2018-08-30 2:07 ` Paul E. McKenney
2018-08-30 2:46 ` Steven Rostedt
2018-08-30 3:23 ` Paul E. McKenney
2018-08-30 16:44 ` Steven Rostedt
2018-08-30 17:35 ` Paul E. McKenney
2018-08-30 17:37 ` Paul E. McKenney
2018-08-30 18:36 ` Steven Rostedt [this message]
2018-08-30 23:12 ` Paul E. McKenney
2018-08-30 23:53 ` Steven Rostedt
2018-08-31 0:09 ` Paul E. McKenney
2018-08-31 0:55 ` Steven Rostedt
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=20180830143617.2fb85e23@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®