public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu/sync: kill rcu_sync_type/gp_type
Date: Wed, 24 Apr 2019 13:37:04 +0200	[thread overview]
Message-ID: <20190424113704.GB16167@redhat.com> (raw)
In-Reply-To: <20190423193306.GU3923@linux.ibm.com>

On 04/23, Paul E. McKenney wrote:
>
> I wordsmithed the commit log and merged in the RCU-bh and RCU checks
> to rcu_sync_is_idle(), with the result shown below.  Does that work
> OK, or did I mess something up?

Yes, thanks!

the additional RCU-bh and RCU checks matches the "or introduce rcu_read_lock_any_held()"
note from the changelog, perhaps it makes some sense...

Just one nit below,

> - * Must be invoked within an RCU read-side critical section whose
> - * flavor matches that of the rcu_sync struture.
> + * Must be invoked within an RCU-sched read-side critical section.
                                ^^^^^^^^^

Given that the actual code:

>  static inline bool rcu_sync_is_idle(struct rcu_sync *rsp)
>  {
> -#ifdef CONFIG_PROVE_RCU
> -	rcu_sync_lockdep_assert(rsp);
> -#endif
> +	RCU_LOCKDEP_WARN(!rcu_read_lock_held() &&
> +			 !rcu_read_lock_bh_held() &&
> +			 !rcu_read_lock_sched_held(),
> +			 "suspicious rcu_sync_is_idle() usage");

does RCU_LOCKDEP_WARN(!rcu_read_lock_any()) the comment should say

	Must be invoked within an RCU read-side critical section of
	any flavor

?

Oleg.


  reply	other threads:[~2019-04-24 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 12:07 [PATCH] rcu/sync: kill rcu_sync_type/gp_type Oleg Nesterov
2019-04-23 19:33 ` Paul E. McKenney
2019-04-24 11:37   ` Oleg Nesterov [this message]
2019-04-24 18:56     ` Paul E. McKenney
2019-04-25 10:29       ` Oleg Nesterov

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=20190424113704.GB16167@redhat.com \
    --to=oleg@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.ibm.com \
    --cc=peterz@infradead.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