On Sun, Jun 11, 2023 at 08:48:36PM +0800, Zorro Lang wrote: > Hi, > > When I tried to do fstests regression test this weekend on latest linux > v6.5-rc5+ (HEAD=64569520920a3ca5d456ddd9f4f95fc6ea9b8b45), nearly all > testing jobs on xfs hang on generic/051 (more than 24 hours, still blocked). > No matter 1k or 4k blocksize, general disk or pmem dev, or any architectures, > or any mkfs/mount options testing, all hang there. Yup, I started seeing this on upgrade to 6.5-rc5, too. xfs/079 generates it, because the fsstress process is crashing when the XFS filesystems shuts down (maybe a SIGBUS from a mmap page fault?) I don't know how reproducable it is yet; these only showed up in my thrusday night testing so I haven't had a chance to triage it yet. > Someone console log as below (a bit long), the call trace doesn't contains any > xfs functions, it might be not a xfs bug, but it can't be reproduced on ext4. AFAICT, the coredump is being done on the root drive (where fsstress is being executed from), not the XFS test/scratch devices that fsstress processes are exercising. I have ext3 root drives for my test machines, so at this point I'm not sure that this is even a filesystem related regression. i.e. it may be a recent regression in the coredump or signal handling code.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
