public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Neeraj Upadhyay <neeraju@codeaurora.org>
Cc: Mukesh Ojha <mojha@codeaurora.org>,
	josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	joel@joelfernandes.org, rcu@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: tree_stall: Correctly unlock root node in rcu_check_gp_start_stall
Date: Thu, 4 Apr 2019 14:07:57 -0700	[thread overview]
Message-ID: <20190404210757.GO14111@linux.ibm.com> (raw)
In-Reply-To: <10b7ba19-9184-a4aa-d609-a644fcbe0503@codeaurora.org>

On Sat, Mar 30, 2019 at 09:14:36AM +0530, Neeraj Upadhyay wrote:
> On 3/30/19 2:57 AM, Paul E. McKenney wrote:
> >On Fri, Mar 29, 2019 at 07:52:15PM +0530, Neeraj Upadhyay wrote:
> >>
> >>
> >>On 3/29/19 6:58 PM, Mukesh Ojha wrote:
> >>>
> >>>On 3/29/2019 4:57 PM, Neeraj Upadhyay wrote:
> >>>>Only unlock the root node, if current node (rnp) is not
> >>>>root node.
> >>>>
> >>>>Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
> >>>
> >>>
> >>>
> >>>>---
> >>>>   kernel/rcu/tree_stall.h | 4 +++-
> >>>>   1 file changed, 3 insertions(+), 1 deletion(-)
> >>>>
> >>>>diff --git a/kernel/rcu/tree_stall.h b/kernel/rcu/tree_stall.h
> >>>>index f65a73a..0651833 100644
> >>>>--- a/kernel/rcu/tree_stall.h
> >>>>+++ b/kernel/rcu/tree_stall.h
> >>>
> >>>
> >>>why this is showing as under tree_stall.h while it is under
> >>>"kernel/rcu/tree.c"
> >>
> >>It's moved in https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?h=dev&id=10462d6f58fb6dbde7563e9343505d98d5bfba3d
> >>
> >>Please see linux-rcu dev tree for other changes, which moves code to
> >>this file.
> >>
> >>
> >>Thanks
> >>Neeraj
> >>
> >>>
> >>>>@@ -630,7 +630,9 @@ static void rcu_check_gp_start_stall(struct
> >>>>rcu_node *rnp, struct rcu_data *rdp,
> >>>>           time_before(j, rcu_state.gp_req_activity + gpssdelay) ||
> >>>>           time_before(j, rcu_state.gp_activity + gpssdelay) ||
> >>>>           atomic_xchg(&warned, 1)) {
> >>>>-        raw_spin_unlock_rcu_node(rnp_root); /* irqs remain disabled. */
> >>>>+        if (rnp_root != rnp)
> >>>>+            /* irqs remain disabled. */
> >>>>+            raw_spin_unlock_rcu_node(rnp_root);
> >>>
> >>>Looks good as it will balance the lock .if it is the root_node,
> >>>which was not there earlier, and unlock was happening without any
> >>>lock on root.
> >>>
> >>>Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
> >
> >Applied, again thank you both!
> >
> >In both cases, I updated the commit log, so please check to make sure
> >that I didn't mess anything up.
> >
> >							Thanx, Paul
> >
> 
> Thanks Paul. One minor comment on https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?h=dev&id=ec6530e763046b6bb1f4c2c2aed49ebc68aae2a0
> 
> 
> "it clearly does not make sense to release
> both rnp->lock and rnp->lock"
> 
> should be rnp->lock and rnp_root->lock

Good eyes, fixed, thank you!

							Thanx, Paul

> Thanks
> Neeraj
> 
> >>>Cheers,
> >>>-Mukesh
> >>>
> >>>>           raw_spin_unlock_irqrestore_rcu_node(rnp, flags);
> >>>>           return;
> >>>>       }
> >>
> >>-- 
> >>QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
> >>member of the Code Aurora Forum, hosted by The Linux Foundation
> >>
> >
> 
> -- 
> QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
> member of the Code Aurora Forum, hosted by The Linux Foundation
> 


      reply	other threads:[~2019-04-04 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 11:27 [PATCH] rcu: tree_stall: Correctly unlock root node in rcu_check_gp_start_stall Neeraj Upadhyay
2019-03-29 13:28 ` Mukesh Ojha
2019-03-29 14:22   ` Neeraj Upadhyay
2019-03-29 21:27     ` Paul E. McKenney
2019-03-30  3:44       ` Neeraj Upadhyay
2019-04-04 21:07         ` Paul E. McKenney [this message]

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=20190404210757.GO14111@linux.ibm.com \
    --to=paulmck@linux.ibm.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=mojha@codeaurora.org \
    --cc=neeraju@codeaurora.org \
    --cc=rcu@vger.kernel.org \
    --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