From: Kunwu Chan <kunwu.chan@hotmail.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
hch <hch@lst.de>
Subject: Re: rcu stalls during fstests runs for xfs
Date: Wed, 28 Jan 2026 17:55:01 +0800 [thread overview]
Message-ID: <IA1PR14MB565903564F4AA105AF6A21099791A@IA1PR14MB5659.namprd14.prod.outlook.com> (raw)
In-Reply-To: <aXdO52wh2rqTUi1E@shinmob>
On 1/26/26 19:30, Shinichiro Kawasaki wrote:
> kernel: xfs/for-next, 51aba4ca399, v6.19-rc5+
> block device: dm-linear on HDD (non-zoned)
> xfs: zoned
I had a quick look at the attached logs. Across the different runs, the
stall traces consistently show CPUs spending extended time in
|mm_get_cid()|along the mm/sched context switch path.
This doesn’t seem to indicate an immediate RCU issue by itself, but it
raises the question of whether context switch completion can be delayed
for unusually long periods under these test configurations.
--
Thanx, Kunwu
next prev parent reply other threads:[~2026-01-28 9:55 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 [this message]
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=IA1PR14MB565903564F4AA105AF6A21099791A@IA1PR14MB5659.namprd14.prod.outlook.com \
--to=kunwu.chan@hotmail.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox