From: Steven Rostedt <rostedt@goodmis.org>
To: Neeraj Upadhyay <neeraju@codeaurora.org>
Cc: paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu/tree: Fix self wakeups for grace period kthread
Date: Mon, 11 Mar 2019 21:50:27 -0400 [thread overview]
Message-ID: <20190311215027.2f3458a1@oasis.local.home> (raw)
In-Reply-To: <1552038378-11166-1-git-send-email-neeraju@codeaurora.org>
On Fri, 8 Mar 2019 15:16:18 +0530
Neeraj Upadhyay <neeraju@codeaurora.org> wrote:
> Update the code to match the comment that self wakeup of
> grace period kthread is allowed from interrupt handler, and
> softirq handler, running in the grace period kthread's
> context. Present code allows self wakeups from all
> interrupt contexts - nmi, softirq and hardirq contexts.
That's not actually the issue. But it appears that we return if we
simply have BH disabled, which I don't think we want, and we don't care
about NMI as NMI should never call this code.
I think your patch is correct, but the change log is not.
-- Steve
>
> Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
> ---
> kernel/rcu/tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index acd6ccf..57cac6d 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -1585,7 +1585,7 @@ static bool rcu_future_gp_cleanup(struct rcu_node *rnp)
> static void rcu_gp_kthread_wake(void)
> {
> if ((current == rcu_state.gp_kthread &&
> - !in_interrupt() && !in_serving_softirq()) ||
> + !in_irq() && !in_serving_softirq()) ||
> !READ_ONCE(rcu_state.gp_flags) ||
> !rcu_state.gp_kthread)
> return;
next prev parent reply other threads:[~2019-03-12 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 9:46 Neeraj Upadhyay
2019-03-12 1:50 ` Steven Rostedt [this message]
2019-03-12 11:55 ` Neeraj Upadhyay
2019-03-12 14:09 ` Paul E. McKenney
2019-03-12 14:56 ` Steven Rostedt
2019-03-12 15:36 ` 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=20190311215027.2f3458a1@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=jiangshanlai@gmail.com \
--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 \
/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