public inbox for rcu@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	Saravana Kannan <saravanak@kernel.org>
Subject: Re: [PATCH RFC] rcutorture: Fully test lazy RCU
Date: Sun, 1 Mar 2026 05:11:51 -0500	[thread overview]
Message-ID: <B0408540-C5C7-4AEE-AF5A-545EA50CF7DD@nvidia.com> (raw)
In-Reply-To: <a7dd04f0-52ba-4543-a159-f989b851906c@paulmck-laptop>

[...]

>>> 3.    Does the rcu_torture_ops structure need a ->call_hurry() field,
>>>   and if so, why?  If not, why not?
>>>
>>> 4.    Your additional questions here!
>>
>> Do we have a reproducer for the splat? If there is a link to the
>> report, I could take a look and investigate.
>
> The splat is on an old kernel where rcutorture does not yet have
> call_rcu_hurry().  So this patch isn't fixing a bug, but rather allegedly
> improving lazy RCU rcutorture testing.

Makes sense! I take it that on a newer kernel, we do see a splat with
just replacing _hurry() with the alternative, but without any other
changes. But either way, this is a nice change, so thanks!

-- 
Joel Fernandes


      reply	other threads:[~2026-03-01 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28  0:39 [PATCH RFC] rcutorture: Fully test lazy RCU Paul E. McKenney
2026-03-01  3:09 ` Joel Fernandes
2026-03-01  4:14   ` Paul E. McKenney
2026-03-01 10:11     ` Joel Fernandes [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=B0408540-C5C7-4AEE-AF5A-545EA50CF7DD@nvidia.com \
    --to=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=saravanak@kernel.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