public inbox for rcu@vger.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "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: Tue, 27 Jan 2026 01:38:24 +0000	[thread overview]
Message-ID: <aXgVljuSfUomyikG@shinmob> (raw)
In-Reply-To: <aXfzNW7cf2ReVDA4@dread.disaster.area>

On Jan 27, 2026 / 10:05, Dave Chinner wrote:
[...]
> IOWs, this looks like some kind of RCU/static key/scheduler
> interaction which may propagate into the block layer if it needs RCU
> synchronisation. Hence it does not appear to have anything to do
> with the filesystem layers, and it is possible the block layer is
> colateral damage, too.
> 
> Probably best to hand this over to the core kernel ppl.

Dave, thank you very much for looking in the logs and sharing your views.
I will wait for comments from RCU experts and keep the effort to recreate
the hangs.

  reply	other threads:[~2026-01-27  1:38 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 [this message]
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
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=aXgVljuSfUomyikG@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox