public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: cheung wall <zzqq0103.hey@gmail.com>,
	"Paul E. McKenney" <paulmck@kernel.org>
Cc: cheung wall <zzqq0103.hey@gmail.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
	Joel Fernandes <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Zqiang <qiang.zhang1211@gmail.com>,
	rcu@vger.kernel.org
Subject: Re: "WARNING in rcu_sr_normal_complete" in Linux Kernel v6.12-rc4
Date: Tue, 28 Jan 2025 10:32:49 +0100	[thread overview]
Message-ID: <Z5ikQeVmVdsWQrdD@pc636> (raw)
In-Reply-To: <Z4kRzMO03mwjqCu2@pc636>

On Thu, Jan 16, 2025 at 03:03:56PM +0100, Uladzislau Rezki wrote:
> Hello, Cheung Wall!
> 
> > 
> > I am writing to report a potential vulnerability identified in the
> > Linux Kernel version v6.12-rc4. This vulnerability was discovered
> > while i was testing the kernel.
> > 
> > Linux Kernel Repository Git Commit:
> > 42f7652d3eb527d03665b09edac47f85fb600924 (tag: v6.12-rc4)
> > 
> > Bug Location: 0010:rcu_sr_normal_complete+0xd0/0x110 kernel/rcu/tree.c:1638
> > 
> > Bug report: https://pastebin.com/kuJ7wnPe
> > 
> > Entire Log: https://pastebin.com/fT42ya0T
> > 
> > Thank you for your time and attention.
> > 
> Do you have a reproducer of this splat?
> 
The reproducer is below:

for (( i=0; i<$LOOPS; i++ )); do
	tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --configs \
	'16*TREE05' --memory 10G --bootargs 'rcutorture.fwd_progress=1' \
	--kconfig "CONFIG_NR_CPUS=4"

	echo "Done $i"
done

Please note, it also requires to modify TREE05:

+# This part is for synchronize_rcu() testing
+rcutorture.nfakewriters=-1
+rcutorture.gp_sync=1
+rcupdate.rcu_normal=1
+rcutree.rcu_normal_wake_from_gp=1

and:

diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
index d26fb1d33ed9..6bc161e1e8ac 100644
--- a/kernel/rcu/rcutorture.c
+++ b/kernel/rcu/rcutorture.c
@@ -4050,6 +4050,10 @@ rcu_torture_init(void)
                                          writer_task);
        if (torture_init_error(firsterr))
                goto unwind;
+
+       if (nfakewriters < 0)
+               nfakewriters = (int) num_possible_cpus();
+
        if (nfakewriters > 0) {
                fakewriter_tasks = kcalloc(nfakewriters,
                                           sizeof(fakewriter_tasks[0]),

--
Uladzislau Rezki

      reply	other threads:[~2025-01-28  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15  2:36 "WARNING in rcu_sr_normal_complete" in Linux Kernel v6.12-rc4 cheung wall
2025-01-16 14:03 ` Uladzislau Rezki
2025-01-28  9:32   ` Uladzislau Rezki [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=Z5ikQeVmVdsWQrdD@pc636 \
    --to=urezki@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=neeraj.upadhyay@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=zzqq0103.hey@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