From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Matthieu Baerts <matttbe@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>, "Paul E. McKenney" <paulmck@kernel.org>,
MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: rcu stalls during fstests runs for xfs
Date: Fri, 6 Feb 2026 10:02:37 +0000 [thread overview]
Message-ID: <aYW6GCmmCFeivAxo@shinmob> (raw)
In-Reply-To: <144e31a9-e29c-4809-af2e-5ac45150d3f7@kernel.org>
On Feb 06, 2026 / 10:33, Matthieu Baerts wrote:
> Hi Shinichiro,
>
> Sorry to jump in, but I *think* our CI for the MPTCP subsystem is
> hitting the same issue.
Hi Matthieu,
> On 30/01/2026 12:16, Shinichiro Kawasaki wrote:
> > 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.
>
> I know it is only one week now, but did you see any effects so far?
No, I do not see any hang so far. And I hope there will be no hang in the
next week either. Fingers crossed...
> On
> my side, I applied the v2 series -- which has been applied i
> tip/sched/urgent -- but I still have issues, and it looks like it is
> even more frequent. Maybe what I see is different. If you no longer see
> the issues on your side after one week, I'm going to start a new thread
> with my issues not to mix them.
>
> Note that in my case, the issue is visible on a system where nested VMs
> are used, with and without KASAN (enabled via debug.config), just after
> having started a VSOCK listening socket via socat.
I applied the v1 series on top of my test target xfs kernel branches enabling
KASAN.
next prev parent reply other threads:[~2026-02-06 10:02 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
2026-02-06 9:33 ` Matthieu Baerts
2026-02-06 10:02 ` Shinichiro Kawasaki [this message]
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=aYW6GCmmCFeivAxo@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=hch@lst.de \
--cc=kunwu.chan@hotmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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.