From: Mukesh Ojha <mojha@codeaurora.org>
To: Neeraj Upadhyay <neeraju@codeaurora.org>,
paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, joel@joelfernandes.org
Cc: 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: Fri, 29 Mar 2019 18:58:22 +0530 [thread overview]
Message-ID: <7a9eed5a-9bcf-460c-abb9-1e9bd6eae102@codeaurora.org> (raw)
In-Reply-To: <1553858828-23097-1-git-send-email-neeraju@codeaurora.org>
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"
> @@ -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>
Cheers,
-Mukesh
> raw_spin_unlock_irqrestore_rcu_node(rnp, flags);
> return;
> }
next prev parent reply other threads:[~2019-03-29 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 11:27 Neeraj Upadhyay
2019-03-29 13:28 ` Mukesh Ojha [this message]
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
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=7a9eed5a-9bcf-460c-abb9-1e9bd6eae102@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraju@codeaurora.org \
--cc=paulmck@linux.vnet.ibm.com \
--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
Powered by JetHome