From: John Garry <john.garry@linux.dev>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [bug report] fstests generic/774 hang again
Date: Tue, 15 Sep 2026 15:48:13 +0100 [thread overview]
Message-ID: <ed224f94-f605-4be0-8a0a-0b3d481e46ae@linux.dev> (raw)
In-Reply-To: <aqkv-2opTlWD6bzU@shinmob>
On 9/15/26 12:48, Shin'ichiro Kawasaki wrote:
> On Sep 15, 2026 / 11:00, John Garry wrote:
>> On 9/15/26 10:34, Shin'ichiro Kawasaki wrote:
>>> I observe the fstests test case generic/774 hangs, when I run it for xfs on 8GiB
>>> TCMU fileio devices. Actually I once reported this hang symptom in last October,
>>> and Darrick and John kindly took some actions [1]. Since then, the hang
>>> disappeared and I have not observed the hang almost one year. However, my test
>>> system started reporting the hang again last week.
>>>
>>> [1] https://lore.kernel.org/linux-xfs/cmk52aqexackyz65phxgme55a3tdrermo3o4skr4lo4pwvvvcp@jmcblnfikbp2/#t
>>
>> This was the series to resolve, I think:
>> https://lore.kernel.org/fstests/176279908967.605950.2192923313361120314.stgit@frogsfrogsfrogs/T/#t
>>
>> As an experiment, can you reduce the file size further, like:
>>
>> --- a/tests/generic/774
>> +++ b/tests/generic/774
>> @@ -29,7 +29,7 @@ aw_bsize=$(_max "$awu_min_write" "$((awu_max_write/4))")
>> fsbsize=$(_get_block_size $SCRATCH_MNT)
>>
>> threads=$(_min "$(($(nproc) * 2 * LOAD_FACTOR))" "100")
>> -filesize=$((aw_bsize * threads * 10))
>> +filesize=$((aw_bsize * threads))
>> depth=$threads
>> aw_io_size=$((filesize / threads))
>> aw_io_inc=$aw_io_size
>
> Thanks for the response. I repeated the test case 100 times with the change
> above, and I did not observe the hang. The change looks avoiding the hang.
>
>>
>>>
>>> FYI, here I attache the kernel message [2].
>>
>> Is mainline baseline hanging, i.e. v7.3-rc2?
>
> I will try this out tomorrow.
thanks
About the kernel code, I am wondering if using IOMAP_DIO_FORCE_WAIT for
CoW-based atomics could help avoid this issue as we seem to be bogged
down in lock contention.
next prev parent reply other threads:[~2026-09-15 14:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:34 [bug report] fstests generic/774 hang again Shin'ichiro Kawasaki
2026-09-15 10:00 ` John Garry
2026-09-15 11:48 ` Shin'ichiro Kawasaki
2026-09-15 14:48 ` John Garry [this message]
2026-09-15 14:50 ` Darrick J. Wong
2026-09-15 15:41 ` John Garry
2026-09-16 10:23 ` John Garry
2026-09-16 22:23 ` Dave Chinner
2026-09-17 8:28 ` John Garry
2026-09-17 21:20 ` Dave Chinner
2026-09-17 6:30 ` Shin'ichiro Kawasaki
2026-09-16 2:53 ` Shin'ichiro Kawasaki
2026-09-16 21:45 ` Dave Chinner
2026-09-17 6:52 ` Shin'ichiro Kawasaki
2026-09-17 10:45 ` Shin'ichiro Kawasaki
2026-09-17 21:24 ` Dave Chinner
2026-09-19 11:53 ` Shin'ichiro Kawasaki
2026-09-21 22:05 ` Dave Chinner
2026-09-25 1:32 ` Shin'ichiro Kawasaki
2026-09-27 21:30 ` Dave Chinner
2026-09-28 2:45 ` Darrick J. Wong
2026-09-22 0:28 ` Darrick J. Wong
2026-09-25 1:38 ` Shin'ichiro Kawasaki
2026-09-25 23:03 ` Darrick J. Wong
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=ed224f94-f605-4be0-8a0a-0b3d481e46ae@linux.dev \
--to=john.garry@linux.dev \
--cc=djwong@kernel.org \
--cc=linux-xfs@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