From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [peterz-queue:sched/lazy] [sched, x86] 74d850cd4c: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print[rcutorture]
Date: Wed, 16 Oct 2024 17:40:48 +0200 [thread overview]
Message-ID: <20241016154048.sdiJ85Zc@linutronix.de> (raw)
In-Reply-To: <202410151544.7d2292c6-lkp@intel.com>
On 2024-10-15 15:47:20 [+0800], kernel test robot wrote:
> Hello,
Hi,
it took me a while to reproduce this because it does not trigger without
the ltp userland and this is not downloaded properly so I had to
workaround it. However…
> [ 98.006999][ T543] busted-torture: rtc: 00000000639e821e ver: 6796 tfle: 0 rta: 6796 rtaf: 0 rtf: 6787 rtmbe: 1 rtmbkf: 0/0 rtbe: 0 rtbke: 0 rtbf: 0 rtb: 0 nt: 89 barrier: 0/0:0 read-exits: 64 nocb-toggles: 0:0
> [ 98.017386][ T543] busted-torture: !!!
> [ 98.017662][ T543] ------------[ cut here ]------------
> [ 98.019330][ T543] WARNING: CPU: 0 PID: 543 at kernel/rcu/rcutorture.c:2258 rcu_torture_stats_print+0x24c/0x610 [rcutorture]
> [ 98.021831][ T543] Modules linked in: rcutorture torture
…
> [ 98.237025][ T543] ------------[ cut here ]------------
> [ 98.238052][ T543] WARNING: CPU: 0 PID: 543 at kernel/rcu/rcutorture.c:2263 rcu_torture_stats_print+0x373/0x610 [rcutorture]
> [ 98.240000][ T543] Modules linked in: rcutorture torture
…
It took me a while to figure out that this test is using
rcu_busted_torture_deferred_free() which in turn invokes the callback
before the grace period. Buh.
So it looks like LAZY preempt triggers this more reliably than the
normal preempt version…
Sebastian
next prev parent reply other threads:[~2024-10-16 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 7:47 kernel test robot
2024-10-16 15:40 ` Sebastian Andrzej Siewior [this message]
2024-10-16 16:12 ` Paul E. McKenney
2024-10-17 6:26 ` Oliver Sang
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=20241016154048.sdiJ85Zc@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.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®