From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Milton Miller <miltonm@bga.com>
Subject: Re: [PATCH 1/4] rcu: Detect uses of rcu read side in extended quiescent states
Date: Thu, 9 Jun 2011 17:23:50 -0700 [thread overview]
Message-ID: <20110610002350.GO2285@linux.vnet.ibm.com> (raw)
In-Reply-To: <1307663247-5397-2-git-send-email-fweisbec@gmail.com>
On Fri, Jun 10, 2011 at 01:47:24AM +0200, Frederic Weisbecker wrote:
> Detect uses of rcu that are not supposed to happen when we
> are in an extended quiescent state.
>
> This can happen for example if we use rcu between the time we
> stop the tick and the time we restart it. Or inside an irq that
> didn't use rcu_irq_enter,exit() or other possible kind of rcu API
> misuse.
>
> v2: Rebase against latest rcu changes, handle tiny RCU as well
Good idea on checking for RCU read-side critical sections happening
in dyntick-idle periods!
But wouldn't it be better to put the checks in rcu_read_lock() and
friends? The problem I see with putting them in rcu_dereference_check()
is that someone can legitimately do something like the following
while in dyntick-idle mode:
spin_lock(&mylock);
/* do a bunch of stuff */
p = rcu_dereference_check(myrcuptr, lockdep_is_held(&mylock));
The logic below would complain about this usage, despite the fact
that it is perfectly safe because the update-side lock is held.
Make sense, or am I missing something?
Thanx, Paul
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Milton Miller <miltonm@bga.com>
> ---
> include/linux/rcupdate.h | 9 +++++++++
> kernel/rcutiny.c | 13 +++++++++++++
> kernel/rcutree.c | 14 ++++++++++++++
> 3 files changed, 36 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> index 9db50df..6cad1f3 100644
> --- a/include/linux/rcupdate.h
> +++ b/include/linux/rcupdate.h
> @@ -388,6 +388,12 @@ extern int rcu_my_thread_group_empty(void);
>
> #endif /* #else #ifdef CONFIG_PROVE_RCU */
>
> +#if defined(CONFIG_PROVE_RCU) && defined(CONFIG_NO_HZ)
> +extern bool rcu_check_extended_qs(void);
> +#else
> +static inline bool rcu_check_extended_qs(void) { return false; }
> +#endif
> +
> /*
> * Helper functions for rcu_dereference_check(), rcu_dereference_protected()
> * and rcu_assign_pointer(). Some of these could be folded into their
> @@ -415,6 +421,9 @@ extern int rcu_my_thread_group_empty(void);
> typeof(*p) *_________p1 = (typeof(*p)*__force )ACCESS_ONCE(p); \
> rcu_lockdep_assert(c, "suspicious rcu_dereference_check()" \
> " usage"); \
> + rcu_lockdep_assert(!rcu_check_extended_qs(), \
> + "use of rcu_dereference_check() in an extended" \
> + " quiescent state"); \
> rcu_dereference_sparse(p, space); \
> smp_read_barrier_depends(); \
> ((typeof(*p) __force __kernel *)(_________p1)); \
> diff --git a/kernel/rcutiny.c b/kernel/rcutiny.c
> index 775d69a..44a2a15 100644
> --- a/kernel/rcutiny.c
> +++ b/kernel/rcutiny.c
> @@ -76,6 +76,19 @@ void rcu_exit_nohz(void)
> rcu_dynticks_nesting++;
> }
>
> +
> +#ifdef CONFIG_PROVE_RCU
> +
> +bool rcu_check_extended_qs(void)
> +{
> + if (!rcu_dynticks_nesting)
> + return true;
> +
> + return false;
> +}
> +
> +#endif
> +
> #endif /* #ifdef CONFIG_NO_HZ */
>
> /*
> diff --git a/kernel/rcutree.c b/kernel/rcutree.c
> index 305dfae..8211527 100644
> --- a/kernel/rcutree.c
> +++ b/kernel/rcutree.c
> @@ -432,6 +432,20 @@ void rcu_irq_exit(void)
> rcu_enter_nohz();
> }
>
> +#ifdef CONFIG_PROVE_RCU
> +
> +bool rcu_check_extended_qs(void)
> +{
> + struct rcu_dynticks *rdtp = &__get_cpu_var(rcu_dynticks);
> +
> + if (atomic_read(&rdtp->dynticks) & 0x1)
> + return false;
> +
> + return true;
> +}
> +
> +#endif /* CONFIG_PROVE_RCU */
> +
> #ifdef CONFIG_SMP
>
> /*
> --
> 1.7.5.4
>
next prev parent reply other threads:[~2011-06-10 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 23:47 [PATCH 0/4 v2] rcu: Detect rcu uses under extended quiescent state, and fix some Frederic Weisbecker
2011-06-09 23:47 ` [PATCH 1/4] rcu: Detect uses of rcu read side in extended quiescent states Frederic Weisbecker
2011-06-10 0:23 ` Paul E. McKenney [this message]
2011-06-10 0:50 ` Frederic Weisbecker
2011-06-17 23:19 ` Paul E. McKenney
2011-06-18 14:23 ` Frederic Weisbecker
2011-06-18 16:04 ` Paul E. McKenney
2011-06-18 16:10 ` Frederic Weisbecker
2011-06-18 16:36 ` Paul E. McKenney
2011-06-09 23:47 ` [PATCH 2/4] nohz: Split extended quiescent state handling from nohz switch Frederic Weisbecker
2011-06-09 23:47 ` [PATCH 3/4] x86: Don't call idle notifier inside rcu extended QS Frederic Weisbecker
2011-06-09 23:47 ` [PATCH 4/4] x86: Call idle_exit() after irq_enter() Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 3:10 [PATCH 0/4] rcu: Detect rcu uses under extended quiescent state, and fix some Frederic Weisbecker
2011-06-06 3:10 ` [PATCH 1/4] rcu: Detect uses of rcu read side in extended quiescent states Frederic Weisbecker
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=20110610002350.GO2285@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).