From: Joel Fernandes <joelagnelf@nvidia.com>
To: Frederic Weisbecker <frederic@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>,
Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: Re: [PATCH 2/2] rcu: Robustify rcu_is_cpu_rrupt_from_idle()
Date: Sat, 22 Mar 2025 18:00:13 +0100 [thread overview]
Message-ID: <2a67f99e-7afd-499f-855c-69ecffd7c390@nvidia.com> (raw)
In-Reply-To: <20250318135619.4300-3-frederic@kernel.org>
On 3/18/2025 2:56 PM, Frederic Weisbecker wrote:
> RCU relies on the context tracking nesting counter in order to determine
> if it is running in extended quiescent state.
>
> However the context tracking nesting counter is not completely
> synchronized with the actual context tracking state:
>
> * The nesting counter is set to 1 or incremented further _after_ the
> actual state is set to RCU not watching.
I agree with patch, but this line is a bit confusing ->nesting is set to 1
*after* the RCU state is set to "watching". Did you mean "watching" ?
But I think you meant "After RCU transitions from a state of not-watching to
watching' instead of 'actual state is set to RCU not watching'..
ct_kernel_entry():
// RCU is not watching here ...
ct_kernel_enter_state(offset);
// ... but is watching here.
WRITE_ONCE(ct->nesting, 1);
> (then we know for sure we interrupted RCU not watching)
>
> * The nesting counter is set to 0 or decremented further _before_ the
> actual state is set to RCU watching.
>
> Therefore it is safe to assume that if ct_nesting() > 0, RCU is not
> watching. But if ct_nesting() <= 0, RCU is watching except for a tiny
> window.
>
> This hasn't been a problem so far because rcu_is_cpu_rrupt_from_idle()
> has only been called from interrupts. However the code is confusing
Agreed, and I could also see the existing code's snippet:
WARN_ON_ONCE(!nesting && !is_idle_task(current));
.. not working if this function were to be called from non-interrupt kernel context.
> and abuses the role of the context tracking nesting counter while there
> are more accurate indicators available.
>
> Clarify and robustify accordingly.
>
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> ---
> kernel/rcu/tree.c | 27 +++++++++++++++++----------
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 79dced5fb72e..90c43061c981 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -367,7 +367,7 @@ EXPORT_SYMBOL_GPL(rcu_momentary_eqs);
> */
> static int rcu_is_cpu_rrupt_from_idle(void)
> {
> - long nesting;
> + long nmi_nesting = ct_nmi_nesting();
>
> /*
> * Usually called from the tick; but also used from smp_function_call()
> @@ -379,21 +379,28 @@ static int rcu_is_cpu_rrupt_from_idle(void)
> /* Check for counter underflows */
> RCU_LOCKDEP_WARN(ct_nesting() < 0,
> "RCU nesting counter underflow!");
> - RCU_LOCKDEP_WARN(ct_nmi_nesting() <= 0,
> - "RCU nmi_nesting counter underflow/zero!");
>
> - /* Are we at first interrupt nesting level? */
> - nesting = ct_nmi_nesting();
> - if (nesting > 1)
> + /* Non-idle interrupt or nested idle interrupt */
> + if (nmi_nesting > 1)
> return false;
>
> /*
> - * If we're not in an interrupt, we must be in the idle task!
> + * Non nested idle interrupt (interrupting section where RCU
> + * wasn't watching).
> */
> - WARN_ON_ONCE(!nesting && !is_idle_task(current));
> + if (nmi_nesting == 1)
> + return true;
>
> - /* Does CPU appear to be idle from an RCU standpoint? */
> - return ct_nesting() == 0;
> + /* Not in an interrupt */
> + if (!nmi_nesting) {
> + RCU_LOCKDEP_WARN(!in_task() || !is_idle_task(current),
> + "RCU nmi_nesting counter not in idle task!");
> + return !rcu_is_watching_curr_cpu();
Makes sense to me and it is also consistent with rcu_watching_snap_in_eqs().
thanks,
- Joel
next prev parent reply other threads:[~2025-03-22 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 13:56 [PATCH 0/2] rcu: Random updates Frederic Weisbecker
2025-03-18 13:56 ` [PATCH 1/2] rcu: Comment on the extraneous delta test on rcu_seq_done_exact() Frederic Weisbecker
2025-03-18 18:37 ` Paul E. McKenney
2025-03-19 19:38 ` Joel Fernandes
2025-03-20 14:15 ` Frederic Weisbecker
2025-03-22 2:06 ` Joel Fernandes
2025-03-22 10:25 ` Frederic Weisbecker
2025-03-22 14:20 ` Joel Fernandes
2025-03-22 14:40 ` Joel Fernandes
2025-03-23 22:05 ` Frederic Weisbecker
2025-03-23 22:57 ` Joel Fernandes
2025-03-18 13:56 ` [PATCH 2/2] rcu: Robustify rcu_is_cpu_rrupt_from_idle() Frederic Weisbecker
2025-03-22 17:00 ` Joel Fernandes [this message]
2025-03-23 22:31 ` Frederic Weisbecker
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=2a67f99e-7afd-499f-855c-69ecffd7c390@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@amd.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®