public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Neeraj Upadhyay <Neeraj.Upadhyay@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, rostedt@goodmis.org,
	"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH rcu 06/11] rcuscale: Provide clear error when async specified without primitives
Date: Wed, 14 Aug 2024 18:19:15 +0530	[thread overview]
Message-ID: <20240814124915.GA1412840@neeraj.linux> (raw)
In-Reply-To: <20240802004308.4134731-6-paulmck@kernel.org>

On Thu, Aug 01, 2024 at 05:43:03PM -0700, Paul E. McKenney wrote:
> Currently, if the rcuscale module's async module parameter is specified
> for RCU implementations that do not have sync primitives such as
> call_rcu(), there will be a series of splats due to calls to a NULL
> pointer.  This commit therefore warns of this situation, but switches
> to non-async testing.
> 

I have changed this to below here [1]. Please let me know if I got it
wrong.

Currently, if the rcuscale module's async module parameter is specified
for RCU implementations that do not have async primitives such as
RCU Tasks Rude, there will be a series of splats due to calls to a NULL
pointer.  This commit therefore warns of this situation, but switches to
non-async testing.


[1] https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/commit/?h=next.14.08.24b&id=22d36840adbcab8fd826a7ca827fd60b708f03de

- Neeraj

> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> ---
>  kernel/rcu/rcuscale.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/rcu/rcuscale.c b/kernel/rcu/rcuscale.c
> index 933014b381ec0..315ced63ec105 100644
> --- a/kernel/rcu/rcuscale.c
> +++ b/kernel/rcu/rcuscale.c
> @@ -525,7 +525,7 @@ rcu_scale_writer(void *arg)
>  			schedule_timeout_idle(torture_random(&tr) % writer_holdoff_jiffies + 1);
>  		wdp = &wdpp[i];
>  		*wdp = ktime_get_mono_fast_ns();
> -		if (gp_async) {
> +		if (gp_async && !WARN_ON_ONCE(!cur_ops->async)) {
>  retry:
>  			if (!rhp)
>  				rhp = kmalloc(sizeof(*rhp), GFP_KERNEL);
> @@ -597,7 +597,7 @@ rcu_scale_writer(void *arg)
>  			i++;
>  		rcu_scale_wait_shutdown();
>  	} while (!torture_must_stop());
> -	if (gp_async) {
> +	if (gp_async && cur_ops->async) {
>  		cur_ops->gp_barrier();
>  	}
>  	writer_n_durations[me] = i_max + 1;
> -- 
> 2.40.1
> 

  reply	other threads:[~2024-08-14 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  0:43 [PATCH rcu 0/11] RCU update-side scalability update test Paul E. McKenney
2024-08-02  0:42 ` [PATCH rcu 02/11] rcuscale: Dump stacks of stalled rcu_scale_writer() instances Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 03/11] rcuscale: Dump grace-period statistics when rcu_scale_writer() stalls Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 04/11] rcu: Mark callbacks not currently participating in barrier operation Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 05/11] rcuscale: Print detailed grace-period and barrier diagnostics Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 06/11] rcuscale: Provide clear error when async specified without primitives Paul E. McKenney
2024-08-14 12:49   ` Neeraj Upadhyay [this message]
2024-08-14 15:09     ` Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 07/11] rcuscale: Make all writer tasks report upon hang Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 08/11] rcuscale: Make rcu_scale_writer() tolerate repeated GFP_KERNEL failure Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 09/11] rcuscale: Use special allocator for rcu_scale_writer() Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 10/11] rcuscale: NULL out top-level pointers to heap memory Paul E. McKenney
2024-08-02  0:43 ` [PATCH rcu 11/11] rcuscale: Count outstanding callbacks per-task rather than per-CPU 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=20240814124915.GA1412840@neeraj.linux \
    --to=neeraj.upadhyay@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.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