Hi, generic/311 consistently fails when executing on a kernel built from next-20231102. The following is the fstests config file that was used during testing. export FSTYP=xfs export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export TEST_LOGDEV=/dev/loop2 export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch export SCRATCH_LOGDEV=/dev/loop3 export USE_EXTERNAL=yes export MKFS_OPTIONS="-f -m crc=1,reflink=1,rmapbt=1, -i sparse=1 -lsize=1g" The following is the contents obtained from 311.out.bad. QA output created by 311 Running test 1 buffered, normal suspend Random seed is 1 ee6103415276cde95544b11b2675f132 device-mapper: suspend ioctl on flakey-logtest failed: Device or resource busy Command failed. failed to suspend flakey-logtest Git bisect revealed the following to be the first bad commit, abcb2b94cce4fb7a8f84278e8da4d726837439d1 Author: Christian Brauner <brauner@xxxxxxxxxx> AuthorDate: Wed Sep 27 15:21:16 2023 +0200 Commit: Christian Brauner <brauner@xxxxxxxxxx> CommitDate: Sat Oct 28 13:29:24 2023 +0200 bdev: implement freeze and thaw holder operations The old method of implementing block device freeze and thaw operations required us to rely on get_active_super() to walk the list of all superblocks on the system to find any superblock that might use the block device. This is wasteful and not very pleasant overall. Now that we can finally go straight from block device to owning superblock things become way simpler. Link: https://lore.kernel.org/r/20231024-vfs-super-freeze-v2-5-599c19f4faac@xxxxxxxxxx Reviewed-by: Darrick J. Wong <djwong@xxxxxxxxxx> Reviewed-by: Jan Kara <jack@xxxxxxx> Signed-off-by: Christian Brauner <brauner@xxxxxxxxxx> -- Chandan
