public inbox for rcu@vger.kernel.org
 help / color / mirror / Atom feed
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>, Thomas Gleixner <tglx@kernel.org>
Subject: Re: rcu stalls during fstests runs for xfs
Date: Fri, 13 Feb 2026 01:26:32 +0000	[thread overview]
Message-ID: <aY54lbpbvATqNqEA@shinmob> (raw)
In-Reply-To: <aXyRRaOBkvENTlBE@shinmob>

Cc+: Thomas,

On Jan 30, 2026 / 20:16, Shin'ichiro Kawasaki wrote:
> On Jan 29, 2026 / 15:19, Paul E. McKenney wrote:
> [...]
> > 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.

Two weeks have passed, and I did not observed the hang! Then I'm confident that
the v1 fix series by Thomas avoided the rcu stall issue in my xfs-zoned test
systems. The series is already in v6.19 kernel tag as v2. Great.

Thomas, just FYI.

I faced mysterious kernel hangs during my regular fstests runs [1]. RCU experts
suggested the hangs might be caused by the recent MMCID changes. I tried your v1
fix patch series "sched/mmcid: Cure mode transition woes", and confirmed it
avoids the hangs. Thank you for the fix. The v2 series is already in v6.19
kernel tag, so this report might not be so valuable, but just in case. (And
thank you again for the additional quick fix for my blktests failure caused by
one of the patches in the series).

[1] https://lore.kernel.org/rcu/aXdO52wh2rqTUi1E@shinmob/

  parent reply	other threads:[~2026-02-13  1:26 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
2026-02-06 11:04                 ` Matthieu Baerts
2026-02-13  1:26             ` Shinichiro Kawasaki [this message]
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=aY54lbpbvATqNqEA@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 \
    --cc=tglx@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