From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Yao Kai <yaokai34@huawei.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [WARNING] RCU stall in sock_def_readable()
Date: Sat, 18 Apr 2026 20:09:51 -0400 [thread overview]
Message-ID: <20260418200951.5962b4f4@fedora> (raw)
In-Reply-To: <20260418192625.279c4e98@fedora>
On Sat, 18 Apr 2026 19:26:25 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Yes, PREEMPT_DYNAMIC is set. I guess I can test it without it set and
> see if the problem goes away. If that's the case, I'll just disable
> that for this one test that keeps failing due to that warning.
This looks to be my solution. I usually can trigger the issue with 2 or
3 runs of tracing hackbench. I just finished running it 10 times and it
hasn't triggered. I'll let it run a few more times but I'm going to
disable PREEMPT_DYNAMIC in my tests, and hopefully it doesn't fail due
to this anymore.
-- Steve
prev parent reply other threads:[~2026-04-19 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 17:27 [WARNING] RCU stall in sock_def_readable() Steven Rostedt
2026-04-17 0:16 ` Paul E. McKenney
2026-04-17 12:43 ` Steven Rostedt
2026-04-17 13:30 ` Steven Rostedt
2026-04-17 19:03 ` Paul E. McKenney
2026-04-18 22:36 ` Steven Rostedt
2026-04-18 23:01 ` Paul E. McKenney
2026-04-18 23:26 ` Steven Rostedt
2026-04-19 0:09 ` Steven Rostedt [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=20260418200951.5962b4f4@fedora \
--to=rostedt@goodmis.org \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=joel@joelfernandes.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=willemb@google.com \
--cc=yaokai34@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.