On Fri, Jun 14, 2024 at 07:27:59PM +0100, Theodore Ts'o wrote: > On Thu, Jun 13, 2024 at 09:16:18PM -0700, Darrick J. Wong wrote: > > > > Amusingly enough, I still have that patch (and generic/1220) in my > > fstests branch, and I haven't seen this problem happen on g/1220 in > > quite a while. > > Remind me what your fstests git repo is again? https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/log/?h=djwong-wtf > The generic/750 test in my patch 2/2 that I sent out reproduces the > problem super-reliably, so long as fsstress actually issues the > io_uring reads and writes. So if you have your patch applied which > suppresses io_uring from fstress by default, you might need to modify > the patch series to force the io_uring, at which point it quite nicely > demonstrates the fsstress ; umount problem. (It sometimes requires > more rounds of fsstress ; umounts before it repro's on the xfs/4k, but > it repro's really nicely on ext4/4k). Hm, your g/750 test mounts and unmounts in a loop, which might be why mine hasn't tripped yet. I'll try applying it and report back. --D > > xfs/4k: > generic/750 Failed 3s > generic/750 Failed 1s > generic/750 Failed 33s > generic/750 Failed 1s > generic/750 Pass 33s > ext4/4k: > generic/750 Failed 3s > generic/750 Failed 2s > generic/750 Failed 7s > generic/750 Failed 2s > generic/750 Failed 7s > > - Ted >
