From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Kunwu Chan <kunwu.chan@hotmail.com>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
hch <hch@lst.de>
Subject: Re: rcu stalls during fstests runs for xfs
Date: Fri, 30 Jan 2026 11:16:23 +0000 [thread overview]
Message-ID: <aXyRRaOBkvENTlBE@shinmob> (raw)
In-Reply-To: <c33c3d3e-a59c-4f5a-a562-13e2cabc2faf@paulmck-laptop>
On Jan 29, 2026 / 15:19, Paul E. McKenney wrote:
[...]
> > > > I have seen the static-key pattern called out by Dave Chinner when running
> > > > KASAN on large systems. We worked around this by disabling KASAN's use
> > > > of static keys. In case you were running KASAN in these tests.
> > >
> > > As to KASAN, yes, I enable it in my test runs. I find three static-keys under
> > > mm/kasan/*. I will think if they can be disabled in my test runs. Thanks.
> >
> > There is a set of Kconfig options that disables static branches. If you
> > cannot find them quickly, please let me know and I can look them up.
Thank you. But now I know the fix series by Thomas is available. I prioritize
the evaluation of the fix series. Later on, I will try disabling the static-keys
if it is required.
>
> And Thomas Gleixner posted an alleged fix to the CID issue here:
>
> https://lore.kernel.org/lkml/20260129210219.452851594@kernel.org/
>
> Please let him know whether or not it helps.
Good to see this fix candidate series, thanks :) I have set up the patches and
started my regular test runs. So far, the hangs have been observed once or twice
a week. To confirm the effect of the fix series, I think two weeks runs will be
required. Once I get the result, will share it on this thread and with Thomas.
next prev parent reply other threads:[~2026-01-30 11:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 11:30 rcu stalls during fstests runs for xfs Shinichiro Kawasaki
2026-01-26 23:05 ` Dave Chinner
2026-01-27 1:38 ` Shinichiro Kawasaki
2026-01-28 9:55 ` Kunwu Chan
2026-01-28 16:42 ` Paul E. McKenney
2026-01-29 5:27 ` Shinichiro Kawasaki
2026-01-29 17:46 ` Paul E. McKenney
2026-01-29 23:19 ` Paul E. McKenney
2026-01-30 11:16 ` Shinichiro Kawasaki [this message]
2026-02-06 9:33 ` Matthieu Baerts
2026-02-06 10:02 ` Shinichiro Kawasaki
2026-02-06 11:04 ` Matthieu Baerts
2026-02-13 1:26 ` Shinichiro Kawasaki
2026-02-20 19:01 ` Joel Fernandes
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=aXyRRaOBkvENTlBE@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=hch@lst.de \
--cc=kunwu.chan@hotmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=paulmck@kernel.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 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.