From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: jiangshanlai@gmail.com, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, kernel-team@lge.com
Subject: Re: [QUESTION] srcu: Remove the SCAN2 state
Date: Wed, 21 Feb 2018 18:11:47 -0800 [thread overview]
Message-ID: <20180222021147.GA2855@linux.vnet.ibm.com> (raw)
In-Reply-To: <1519257447-4232-1-git-send-email-byungchul.park@lge.com>
On Thu, Feb 22, 2018 at 08:57:27AM +0900, Byungchul Park wrote:
> Hello,
>
> I'm sorry for bothering you, and I seem to be obviously missing
> something, but I'm really wondering why we check try_check_zero()
> again in the state, SCAN1, for the previous srcu_idx.
>
> I mean, since we've already checked try_check_zero() in the previous
> grace period and gotten 'true' as a return value, all readers who see
> the flipped idx via srcu_flip() won't update the src_{lock,unlock}_count
> for the previous idx until it gets flipped back again.
>
> Is there any reasons we check try_check_zero() again in the state, SCAN1?
> Is there any problems if the following patch's applied?
Indeed there are! Removing the second scan exposes us to a nasty race
condition where a reader is preempted (or interrupted or whatever) just
after fetching its counter. A detailed explanation for an essentially
equivalent race in userspace RCU may be found on the second column of
page 7 of this PDF:
http://www.computer.org/cms/Computer.org/dl/trans/td/2012/02/extras/ttd2012020375s.pdf
But please let me know if I am missing the point of your patch below.
Thanx, Paul
> Thanks in advance,
> Byungchul
>
> ---
> kernel/rcu/srcutree.c | 16 +---------------
> 1 file changed, 1 insertion(+), 15 deletions(-)
>
> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> index 39e50fe..215c44a 100644
> --- a/kernel/rcu/srcutree.c
> +++ b/kernel/rcu/srcutree.c
> @@ -1125,24 +1125,10 @@ static void srcu_advance_state(struct srcu_struct *sp)
> mutex_unlock(&sp->srcu_gp_mutex);
> return; /* Someone else started the grace period. */
> }
> - }
> -
> - if (rcu_seq_state(READ_ONCE(sp->srcu_gp_seq)) == SRCU_STATE_SCAN1) {
> - idx = 1 ^ (sp->srcu_idx & 1);
> - if (!try_check_zero(sp, idx, 1)) {
> - mutex_unlock(&sp->srcu_gp_mutex);
> - return; /* readers present, retry later. */
> - }
> srcu_flip(sp);
> - rcu_seq_set_state(&sp->srcu_gp_seq, SRCU_STATE_SCAN2);
> }
>
> - if (rcu_seq_state(READ_ONCE(sp->srcu_gp_seq)) == SRCU_STATE_SCAN2) {
> -
> - /*
> - * SRCU read-side critical sections are normally short,
> - * so check at least twice in quick succession after a flip.
> - */
> + if (rcu_seq_state(READ_ONCE(sp->srcu_gp_seq)) == SRCU_STATE_SCAN1) {
> idx = 1 ^ (sp->srcu_idx & 1);
> if (!try_check_zero(sp, idx, 2)) {
> mutex_unlock(&sp->srcu_gp_mutex);
> --
> 1.9.1
>
next prev parent reply other threads:[~2018-02-22 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 23:57 [QUESTION] srcu: Remove the SCAN2 state Byungchul Park
2018-02-22 2:11 ` Paul E. McKenney [this message]
2018-02-22 5:05 ` Byungchul Park
2018-02-22 16:54 ` 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=20180222021147.GA2855@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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