From: Oliver Sang <oliver.sang@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Frederic Weisbecker <frederic@kernel.org>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [paulmckrcu:dev.2024.11.01a] [rcutorture] 622baf5d79: WARNING:at_kernel/rcu/rcutorture.c:#rcutorture_one_extend_check[rcutorture]
Date: Thu, 7 Nov 2024 14:28:27 +0800 [thread overview]
Message-ID: <ZyxeC9WVcbdTAu0x@xsang-OptiPlex-9020> (raw)
In-Reply-To: <1092459d-48e2-4839-a84d-c38d96fa2a36@paulmck-laptop>
hi, Paul,
On Wed, Nov 06, 2024 at 12:07:37PM -0800, Paul E. McKenney wrote:
> On Tue, Nov 05, 2024 at 01:00:53PM +0800, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed "WARNING:at_kernel/rcu/rcutorture.c:#rcutorture_one_extend_check[rcutorture]" on:
> >
> > commit: 622baf5d79169496973d50fc43636469e6af02b7 ("rcutorture: Make rcutorture_one_extend() check reader state")
> > https://github.com/paulmckrcu/linux dev.2024.11.01a
>
> This is an old commit that failed to handle any torture_type other than
> "rcu", including the "srcu" that you tested with. It has since been
> replaced by a series of newer commits fixing this and other bugs, with
> the current version here:
>
> c815d319a933 ("rcutorture: Make rcutorture_one_extend() check reader state")
>
> Does this one work for you?
yes, this one works. issue gone when we run same test case up to 20 times.
d5e74d8e46e8e45c 622baf5d79169496973d50fc436 c815d319a9331530032be3df69c
---------------- --------------------------- ---------------------------
fail:runs %reproduction fail:runs %reproduction fail:runs
| | | | |
:6 100% 6:6 0% :20 dmesg.EIP:rcutorture_one_extend_check
:6 100% 6:6 0% :20 dmesg.WARNING:at_kernel/rcu/rcutorture.c:#rcutorture_one_extend_check[rcutorture]
thanks!
>
> Either way, thank you for your testing efforts!
>
> Thanx, Paul
>
next prev parent reply other threads:[~2024-11-07 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 5:00 kernel test robot
2024-11-06 20:07 ` Paul E. McKenney
2024-11-07 6:28 ` Oliver Sang [this message]
2024-11-07 14:01 ` Paul E. McKenney
2024-11-07 14:06 ` Oliver Sang
2024-11-07 14:17 ` 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=ZyxeC9WVcbdTAu0x@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@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
all inboxes | Powered by JetHome®