)]}' { "log": [ { "commit": "5a9cd3ef1b330a920d288bc3bac1342c9e9e3aa6", "tree": "0b3ccfefad0157fefc9f837bcad45da2dcf74fae", "parents": [ "97faf40fc28dd3f14a298dbeb540c2ae3811cdfb" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Sat Aug 16 15:29:09 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Aug 17 16:44:05 2025 +0800" }, "message": "f2fs/012: adapt lookup_mode\u003dx mount option\n\nw/ below change [1], f2fs will enable lookup_mode\u003dperf by default, it\nwill change f2fs dirent lookup method from linear based lookup to hash\nbased lookup.\n\nSo that, f2fs will ignore sb.s_encoding_flags by default, which is not\ncompatible w/ f2fs/012 testcase, in where it will control lookup method\nby configuring this flag w/ fsck.f2fs.\n\nTo avoid failure of f2fs/012, let\u0027s check whether f2fs has supported\n\"lookup_mode\u003dauto\" mount option, mount w/ the option if it can,\notherwise, don\u0027t.\n\n[1] https://lore.kernel.org/linux-f2fs-devel/20250805065228.1473089-1-chullee@google.com\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Daniel Lee \u003cchullee@google.com\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "97faf40fc28dd3f14a298dbeb540c2ae3811cdfb", "tree": "a0c437d9ff7237e9eca9a7f4b9991000e1a49f35", "parents": [ "7d38f690bf8556345cd1c499d87946327b40247d" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Fri Aug 15 16:14:05 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:12:13 2025 +0800" }, "message": "f2fs: do sanity check on i_xattr_nid\n\nThis is a regression test:\n1. create directory\n2. add a new xattr entry to create xattr node\n3. use inject.f2fs to inject nid of xattr node w/ ino in a file\n4. check whether f2fs kernel module will detect and report such\n corruption in the file\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "7d38f690bf8556345cd1c499d87946327b40247d", "tree": "3d557cea5ea2ed9e636a8f11eb2f46e4a81fe8f1", "parents": [ "3c4fce2127c92382d728c3e988a6e3f8af962d2b" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Fri Aug 15 16:14:04 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:12:13 2025 +0800" }, "message": "f2fs: do sanity check on mapping table\n\nThis is a regression test:\n1. create a file\n2. write file to create a direct node at special offset\n3. use inject.f2fs to inject nid of direct node w/ ino of the inode\n4. check whether f2fs kernel module will detect and report such\n corruption in the fil\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3c4fce2127c92382d728c3e988a6e3f8af962d2b", "tree": "fb3436c35c75364e179ee12c248ab171efad617d", "parents": [ "785d75ac491864442631f148d9b37115aa09e83c" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Fri Aug 15 16:14:03 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:12:13 2025 +0800" }, "message": "f2fs: check data eof after partial truncation on compressed cluster\n\nThis is a regression testcase, it is added to check below case\nand its variants:\n- write 16k data into compressed file (data will be compressed)\n- truncate file to 12k (truncate partial data in compressed cluster)\n- truncate file to 20k\n- verify data in range of [12k, 16k] to see whether data is all zero\nor not\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "785d75ac491864442631f148d9b37115aa09e83c", "tree": "952c3bdee69b7097d1008f3ec6ca057bd7de88af", "parents": [ "f1cb492c2b65c4e944e23cc173dff2e29104a47f" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Mon Aug 04 19:40:16 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:11:48 2025 +0800" }, "message": "f2fs: test mount options for zoned device\n\nAs f2fs changes to use new mount APIs, let\u0027s add a new testcase\nto check mount result for special mount options for zoned device\nand their combinations, in order to detect any inconsistency during\nmount.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "f1cb492c2b65c4e944e23cc173dff2e29104a47f", "tree": "ba14c1dfcf78314a913ad72c8105c4fd77b34538", "parents": [ "88aa818b3325477eec06e968bcf4f712137d4b94" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Mon Aug 04 19:40:15 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:11:25 2025 +0800" }, "message": "f2fs: test special mount options\n\nAs f2fs changes to use new mount APIs, let\u0027s add a new testcase\nto check mount result for all f2fs supported special mount options\nand their combinations, in order to detect any inconsistency during\nmount.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "88aa818b3325477eec06e968bcf4f712137d4b94", "tree": "7b31243b718ac7411f6526ef185e504ccbb63395", "parents": [ "b076a3a72941538f6d42a6a7c993768562b65a59" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Mon Aug 04 19:40:14 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:11:06 2025 +0800" }, "message": "f2fs: test common mount options\n\nAs f2fs changes to use new mount APIs, let\u0027s add a new testcase\nto check mount result for all f2fs supported common mount options\nand their combinations, in order to detect any inconsistency during\nmount.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "b076a3a72941538f6d42a6a7c993768562b65a59", "tree": "453eaa15710788a72e3229ab841c89a317a3bc25", "parents": [ "3e802fc7c387b06b1f64e09ed90aaa7f99bbb5a8" ], "author": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Aug 15 22:45:55 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 16 00:09:31 2025 +0800" }, "message": "overlay/005: only run for xfs underlying fs\n\nWhen we runs overlay/005 on a system without xfs module, it always\nfails as \"unknown filesystem type xfs\", due to this case require xfs\nto be the underlying fs explicitly:\n\n $MKFS_XFS_PROG -f -n ftype\u003d1 $upper_loop_dev \u003e\u003e$seqres.full 2\u003e\u00261\n\nSo notrun this case if the underlying fs isn\u0027t \u0027xfs\u0027.\n\nReported-by: Philip Daly \u003cpdaly@redhat.com\u003e\nAcked-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3e802fc7c387b06b1f64e09ed90aaa7f99bbb5a8", "tree": "8a90eabd6b48a76143be19ba81d3eee8f1d08d7c", "parents": [ "00dced3f673035b8522d20ebe7ab3b68de21d08a" ], "author": { "name": "Brian Foster", "email": "bfoster@redhat.com", "time": "Thu Aug 07 10:56:26 2025 -0400" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Tue Aug 12 16:34:03 2025 +0800" }, "message": "xfs: test iomap zero range via fsx and error tag\n\niomap supports a zero range operation based on buffered writes. This\nmechanism is used in limited spots, such as partial block zeroing,\netc., because usually for larger zeroing ops it is more efficient to\npunch a hole and allocate unwritten extents.\n\nThis means iomap zero range has limited production test coverage\neven though it has some particular corner cases that warrant test\ncoverage. XFS supports an error injection knob to force use of iomap\nzero range on fallocate zero range operations. Add a test to run fsx\nwith this knob enabled to provide more zeroing test coverage.\n\nSigned-off-by: Brian Foster \u003cbfoster@redhat.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "00dced3f673035b8522d20ebe7ab3b68de21d08a", "tree": "222e321e852c95dd5e953ee3709155f9d1e52c59", "parents": [ "3d57f543ae0c149eb460574dcfb8d688aeadbfff" ], "author": { "name": "John Garry", "email": "john.g.garry@oracle.com", "time": "Thu Jul 31 09:18:13 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Tue Aug 12 16:29:12 2025 +0800" }, "message": "generic/765: modify some steps to fix test\n\nNow that multi-block atomics writes are supported, some of the test steps\nare failing. Those steps relied on supporting single-block atomic writes\nonly.\n\nThe current test steps are as follows:\na. Ensure statx for bdev returns same awu_min/max as from sysfs\nb. test mkfs for each size of bdev atomic writes capabilities and supported\n FS block size\nc. Ensure atomic limits for file match block size for each in b.\nd. Ensure that we can atomic write block size for each in b.\ne. Ensure that we cannot write file for 2* bdev awu_max or bdev awu_max /2\n\nMake test pass again by:\n1. Modify c. to ensure file awu_max \u003e\u003d block size\n2. dropping e. We already have tests to ensure that we can only write a\n size \u003e\u003d awu_min and \u003c\u003d awu_max in generic/767\n\nSigned-off-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3d57f543ae0c149eb460574dcfb8d688aeadbfff", "tree": "6f68e6ad04769452fdd7c602622dd8e5d0f143ba", "parents": [ "8b81cf5ce725bdd0b725abeb8e333cb547a8569b" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:09:48 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 22:15:17 2025 +0800" }, "message": "xfs/838: actually force usage of the realtime device\n\nActually force the filesystem to create testfile as a realtime file so\nthat the test does anything useful.\n\nCc: fstests@vger.kernel.org # v2025.07.13\nFixes: 7ca990e22e0d61 (\"xfs: more multi-block atomic writes tests\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "8b81cf5ce725bdd0b725abeb8e333cb547a8569b", "tree": "50b3a17a6366e23be19d3e121a3609582673bae4", "parents": [ "ca57558daefe374a04bfceee5780c5765382e041" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:09:32 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 22:15:17 2025 +0800" }, "message": "generic/767: allow on any atomic writes filesystem\n\nThis test now works correctly for any atomic writes geometry since we\ncontrol all the parameters. Remove this restriction so that we can get\nminimal testing on ext4 and fuse2fs.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "ca57558daefe374a04bfceee5780c5765382e041", "tree": "764930017d575cd19a02704662a7cf67adb33f2e", "parents": [ "86950a4e23c176d88b27cfd06039bb4d88b520ff" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:09:17 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 22:15:17 2025 +0800" }, "message": "generic/767: only test the hardware atomic write unit\n\nThis test sets up scsi_debug so that we can test the fs and block layer\ncode for hardware-accelerated atomic writes (and not just a software\nfallback). However, the userspace ABI for detecting atomic write\ngeometry has changed since the start of development (to include said\nsoftware fallback) so we must add some extra code to find the real\nhardware capabilities, and base the write sizes based on that.\n\nThis fixes a test failure with 32k blocksizes because the advertised\natomic_write_unit_max is 128M and fallocate quickly runs out of space.\n\nWhile we\u0027re at it fix a stupid variable usage bug in the loop.\n\nCc: fstests@vger.kernel.org # v2025.07.13\nFixes: fa8694c823d853 (\"generic: various atomic write tests with hardware and scsi_debug\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "86950a4e23c176d88b27cfd06039bb4d88b520ff", "tree": "11e6e0cf60b72ed6530c1c07dd6deaa792cdd4d9", "parents": [ "dca21d3724df983fd8dccdf2b5bfcd99c073f786" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:09:01 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 22:15:17 2025 +0800" }, "message": "generic/767: require fallocate support\n\nThis test fails on filesystems that don\u0027t support fallocate, so screen\nthem out.\n\nCc: fstests@vger.kernel.org # v2025.07.13\nFixes: fa8694c823d853 (\"generic: various atomic write tests with hardware and scsi_debug\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "dca21d3724df983fd8dccdf2b5bfcd99c073f786", "tree": "d6b55f276c68642d273485aa014cc23faff59610", "parents": [ "aa14b84a8d1a2f5eae2d5c46e14dc52fe631b021" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:10:35 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 04:19:02 2025 +0800" }, "message": "xfs/432: fix metadump loop device blocksize problems\n\nMake sure the lba size of the loop devices created for the metadump\ntests actually match that of the real SCRATCH_ devices or else the tests\nwill fail.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "aa14b84a8d1a2f5eae2d5c46e14dc52fe631b021", "tree": "4ac020c0370df9407e785b5cd50a0d7bdbc711d1", "parents": [ "d8b702f89e01fad5a67952833e2ef838a3436e62" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jul 29 13:10:19 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 04:19:02 2025 +0800" }, "message": "xfs/259: try to force loop device block size\n\nStarting with 6.15-rc1, loop devices created with directio mode enabled\nwill set their logical block size to whatever STATX_DIO_ALIGN on the\nhost filesystem reports. If you want fstests to set up loop devices in\ndirectio mode and TEST_DEV is a block device with 4k sectors, this will\ncause conflicts with this test\u0027s usage of mkfs with different block\nsizes. Enhance the existing _create_loop_device so that tests can force\nthe loop device block size to 512 bytes, which is implied by scenarios\nsuch as \"device size is 4T - 2048 bytes\".\n\nAlso fix xfs/078 which simply needs the blocksize to be set.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d8b702f89e01fad5a67952833e2ef838a3436e62", "tree": "c9a1fe4bf6bf9cfa3fabc4a828ce0d27b2451a26", "parents": [ "9f6c59e0d485e6a107cf51d7ee0c8e79b94f1809" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Wed Jul 30 20:21:41 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 03:51:14 2025 +0800" }, "message": "generic: test fsync of file with 0 links and extents\n\nCreate two files, the first one with some data, and then fsync both\nfiles. The first file is fsynced after removing its hardlink. After a\npower failure we expect the fs to be mountable and for only the second\nfile to be present.\n\nThis exercises an issue found in btrfs and fixed by the following patch:\n\n btrfs: fix log tree replay failure due to file with 0 links and extents\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "9f6c59e0d485e6a107cf51d7ee0c8e79b94f1809", "tree": "38670253403be9d9cced96e9da7c77cd229c4cc7", "parents": [ "5dae2b3ca547b578c9306550f4936f01b469e3ff" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Wed Jul 30 19:28:26 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 03:11:50 2025 +0800" }, "message": "xfs/189: fix remount barrier test failure\n\n_test_remount_barrier() is skipped on kernels newer than v4.19 where the\nbarrier options have been removed, and this is detected by matching the\nmount command output for a \"bad option\" error.\n\nRecent util-linux commit 9da5644e414c (\"libmount: report kernel message\nfrom new API\"), which was introduced in v2.41 release changed that error\nmessage from the old hardcoded one:\n\n mount: /mnt/scratch: mount point not mounted or bad option.\n\nto the newer, and more specific coming from the kernel:\n\n mount: /mnt/scratch: fsconfig() failed: xfs: Unknown parameter \u0027barrier\u0027.\n\nUpdate the test to account for that change so that the unsupported\noptions can be properly detected again and for this part of the test to\nbe skipped successfully.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "5dae2b3ca547b578c9306550f4936f01b469e3ff", "tree": "8ca33826c76b2d771719663b423d60936201b4d0", "parents": [ "57e68bd5c6bb93be7ef64e847ac51dc0d1e678f3" ], "author": { "name": "Boris Burkov", "email": "boris@bur.io", "time": "Wed Jul 30 16:03:07 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Aug 02 02:57:43 2025 +0800" }, "message": "btrfs/301: enhance nested simple quotas test\n\nWe had a bug with qgroup accounting with 2+ layers, which was most\neasily detected with a slightly more complex nested squota hierarchy.\nMake the nested squota test case a tiny bit more complex to capture this\ntest as well.\n\nThe kernel patch that this change exercises is:\n btrfs: fix iteration bug in __qgroup_excl_accounting()\n\nSigned-off-by: Boris Burkov \u003cboris@bur.io\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "57e68bd5c6bb93be7ef64e847ac51dc0d1e678f3", "tree": "bee85286290db99293fdac70096122286d9d5472", "parents": [ "c8434d36096dd7d1121f5bce4011f0e0db09ed9d" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Jul 24 13:05:59 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jul 31 16:55:23 2025 +0800" }, "message": "generic/211: verify if the filesystem being tested supports in place writes\n\nThe test currently assumes the filesystem can do in place writes (no\nCopy-On-Write, no allocation of new extents) when overwriting a file.\nWhile that is the case for most filesystems in most configurations, there\nare exceptions such as zoned xfs where overwriting results in allocating\nnew extents for the new data.\n\nSo make the test check that in place writes are supported and skip the\ntest if they are not supported.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "c8434d36096dd7d1121f5bce4011f0e0db09ed9d", "tree": "a1e1688b8ab6e856a6fbbe0c0ec6114159be2260", "parents": [ "2e00b85742d654c6408d4c1d09b78fa72753cd3a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jul 19 23:59:44 2025 -0400" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jul 31 16:55:20 2025 +0800" }, "message": "ext4/028: require that the scratch file system has the extent feature enabled\n\nIf the file system configuration has journalling enabled, but doesn\u0027t\nhave the extent feature enabled (e.g., when testing the ext3\nconfiguration) the test will fail since _scratch_populate_cached\ncreates files with extents enabled. So add a check to skip the test\nin that case.\n\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "2e00b85742d654c6408d4c1d09b78fa72753cd3a", "tree": "6cb417e654c56b41727c097a9162ea51d50a4b6d", "parents": [ "43128a0c543b86cfe8c95280965ba532a413b10d" ], "author": { "name": "Ojaswin Mujoo", "email": "ojaswin@linux.ibm.com", "time": "Fri Jul 11 23:57:44 2025 +0530" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jul 12 16:55:07 2025 +0800" }, "message": "generic/365: Add fix hint for ext4\n\nThis test fails on ext4 if the commit 4a622e4d477b\nis missing in the kernel. Add this hint.\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "43128a0c543b86cfe8c95280965ba532a413b10d", "tree": "d15946f5dea50afebecd6952023e43cf1866578d", "parents": [ "5408cc794fe638e78aa0080dd55fd0e65d4319bb" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Fri Jul 11 18:13:05 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jul 12 16:51:42 2025 +0800" }, "message": "btrfs/282: use timed writes to make sure scrub has enough run time\n\n[FAILURE]\nTest case btrfs/282 still fails on some setup:\n\n output mismatch (see /opt/xfstests/results//btrfs/282.out.bad)\n --- tests/btrfs/282.out\t2025-06-27 22:00:35.000000000 +0200\n +++ /opt/xfstests/results//btrfs/282.out.bad\t2025-07-08 20:40:50.042410321 +0200\n @@ -1,3 +1,4 @@\n QA output created by 282\n wrote 2147483648/2147483648 bytes at offset 0\n XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)\n +scrub speed 2152038400 Bytes/s is not properly throttled, target is 1076019200 Bytes/s\n ...\n (Run diff -u /opt/xfstests/tests/btrfs/282.out /opt/xfstests/results//btrfs/282.out.bad to see the entire diff)\n\n[CAUSE]\nChecking the full output, it shows the scrub is running too fast:\n\nStarting scrub on devid 1\nscrub done for c45c8821-4e55-4d29-8172-f1bf30b7182c\nScrub started: Tue Jul 8 20:40:47 2025\nStatus: finished\nDuration: 0:00:00 \u003c\u003c\u003c\nTotal to scrub: 2.00GiB\nRate: 2.00GiB/s\nError summary: no errors found\nStarting scrub on devid 1\nscrub done for c45c8821-4e55-4d29-8172-f1bf30b7182c\nScrub started: Tue Jul 8 20:40:48 2025\nStatus: finished\nDuration: 0:00:01\nTotal to scrub: 2.00GiB\nRate: 2.00GiB/s\nError summary: no errors found\n\nThe original run takes less than 1 seconds, making the scrub rate\ncalculation very unreliable, no wonder the speed limit is not able to\nproperly work.\n\n[FIX]\nInstead of using fixed 2GiB file size, let the test create a filler for\n4 seconds with direct IO, this would more or less ensure the scrub will\ntake 4 seconds to run.\n\nWith 4 seconds as run time, the scrub rate can be calculated more or\nless reliably.\n\nFurthermore since btrfs-progs currently only reports scrub duration in\nseconds, to prevent problems due to 1 second difference, enlarge the\ntolerance to +/- 25%, to be extra safe.\n\nOn my testing VM, the result looks like this:\n\nStarting scrub on devid 1\nscrub done for b542bdfb-7be4-44b3-add0-ad3621927e2b\nScrub started: Fri Jul 11 09:13:31 2025\nStatus: finished\nDuration: 0:00:04\nTotal to scrub: 2.72GiB\nRate: 696.62MiB/s\nError summary: no errors found\nStarting scrub on devid 1\nscrub done for b542bdfb-7be4-44b3-add0-ad3621927e2b\nScrub started: Fri Jul 11 09:13:35 2025\nStatus: finished\nDuration: 0:00:08\nTotal to scrub: 2.72GiB\nRate: 348.31MiB/s\nError summary: no errors found\n\nHowever this exposed a new failure mode, that if the storage is too\nfast, like the original report, that the initial 4 seconds write can\nfill the fs and exit early.\n\nIn that case we have no other solution but skipping the test case.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "5408cc794fe638e78aa0080dd55fd0e65d4319bb", "tree": "1221e893ece7f2b126e809f0508905e1aac180e9", "parents": [ "9615d021e95eaafb3762289a69aa7245cff7dc7d" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Jul 10 18:03:43 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:44 2025 +0800" }, "message": "generic: test overwriting file with mmap on a full filesystem\n\nTest that overwriting a file with mmap when the filesystem has no more\nspace available for data allocation works. The motivation here is to check\nthat NOCOW mode of a COW filesystem (such as btrfs) works as expected.\n\nThis currently fails with btrfs but it\u0027s fixed by a kernel patch that has\nthe subject:\n\n btrfs: fix -ENOSPC mmap write failure on NOCOW files/extents\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "9615d021e95eaafb3762289a69aa7245cff7dc7d", "tree": "0f21bcea70524fc3262dfa8ace6406978b8959d6", "parents": [ "a673bfe9fb0649d7e3bfc3fd8ae83e3874f238f4" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Wed Jul 02 14:23:12 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:39 2025 +0800" }, "message": "generic/050: add a workaround for btrfs\n\n[BUG]\nWith the incoming btrfs shutdown ioctl/remove_bdev callback support,\nbtrfs can be tested with the shutdown group.\n\nBut test case generic/050 still fails on btrfs with shutdown support:\n\ngeneric/050 1s ... - output mismatch (see /home/adam/xfstests/results//generic/050.out.bad)\n --- tests/generic/050.out\t2022-05-11 11:25:30.763333331 +0930\n +++ /home/adam/xfstests/results//generic/050.out.bad\t2025-06-30 10:22:21.752068622 +0930\n @@ -13,9 +13,7 @@\n setting device read-only\n mounting filesystem that needs recovery on a read-only device:\n mount: device write-protected, mounting read-only\n -mount: cannot mount device read-only\n unmounting read-only filesystem\n -umount: SCRATCH_DEV: not mounted\n mounting filesystem with -o norecovery on a read-only device:\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/generic/050.out /home/adam/xfstests/results//generic/050.out.bad\u0027 to see the entire diff)\nRan: generic/050\n\n[CAUSE]\nThe test case generic/050 has several different golden output depending\non the fs features.\n\nFor fses which requires data write (e.g. replay the journal) during\nmount, mounting a read-only block device should fail.\nAnd that is the default golden output.\n\nHowever for btrfs, although it has something similar to a journal, aka\nlog tree, it\u0027s not the traditional journal which is used to protect\nmetadata update.\n\nThe log tree of btrfs is mostly for speeding up fsync() without syncing\nthe full fs.\n\nThis means several things are different with btrfs:\n\n- Regular metadata update won\u0027t cause dirty log tree\n The workload here is just touching several files, which will not cause\n the creation of btrfs log tree.\n\n And the metadata consistency is protected by metadata COW, not\n journal.\n\n- FLUSHLOG shutdown flag will cause btrfs to commit the current\n transaction\n And above new files are recorded in the current transaction, meaning\n those new files will be fully written by a FLUSHLOG shutdown.\n\nThis means, unlike fses using traditional journals, touching files then\nshutdown with FLUSHLOG will not cause any dirty log tree.\n\nThis makes btrfs acts like it doesn\u0027t support metadata journaling, at\nleast for this particular test case.\n\n[FIX]\nSince the workload here will not cause btrfs to generate a log tree,\nmeaning after the shutdown, the fs can still be mounted RO even the\nblock device is read-only.\n\nSo here we have to make an exception for btrfs, that it has to go\nthrough the \"nojournal\" feature.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a673bfe9fb0649d7e3bfc3fd8ae83e3874f238f4", "tree": "af99be18fcc00c8219eed272d39b32d9d3935216", "parents": [ "d06bd62c4c4258d1cf63d94a2bf046feb846ea25" ], "author": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Mon Jun 23 04:39:47 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:39 2025 +0800" }, "message": "common/rc: _add_dmesg_filter returns when RESULT_DIR is null\n\nI always hit below error on a system with readonly rootfs:\n\n ++ _xfs_prepare_for_eio_shutdown /dev/loop0\n ...\n ++ _add_dmesg_filter \u0027Internal error\u0027\n ++ local \u0027regexp\u003dInternal error\u0027\n ++ local filter_file\u003d/dmesg_filter\n ++ \u0027[\u0027 \u0027!\u0027 -e /dmesg_filter \u0027]\u0027\n ++ echo \u0027Internal error\u0027\n ./common/rc: line 4716: /dmesg_filter: Read-only file system\n\nThe RESULT_DIR is null, due to xfstests/check calls _test_mount and\n_scratch_mount before RESULT_DIR creation. And _test_mount does\n_prepare_for_eio_shutdown -\u003e _xfs_prepare_for_eio_shutdown -\u003e\n_add_dmesg_filter \"Internal error\" when RESULT_DIR is null.\n\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d06bd62c4c4258d1cf63d94a2bf046feb846ea25", "tree": "70581e6a3ca39fa3585de4fc9487cddd721cea9b", "parents": [ "eb0d2b299ded0992d197121c450baad2868a1925" ], "author": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Mon Jun 23 04:39:46 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:39 2025 +0800" }, "message": "common/rc: remove useless _pgrep funcion\n\nThe _pgrep() function isn\u0027t used anymore, remove it.\n\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "eb0d2b299ded0992d197121c450baad2868a1925", "tree": "3651df061520d36db962d3c90d6af7ee4e7dc8d3", "parents": [ "a9dc5ac464764d8c41ffbfe5f74e27b2aca41c29" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:41:20 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:39 2025 +0800" }, "message": "xfs/259: drop the 512-byte fsblock logic from this test\n\nV5 filesystems do not support 512-byte fsblocks, and mkfs.xfs has long\ndefaulted to V5 filesystems. Drop the 512 from the test loops, which\nmeans we can get rid of all the _fs_has_crcs logic. As a further\ncleanup, use the truncate -s command to create the sparse file instead\nof dd since even RHEL7 supports the -s switch.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a9dc5ac464764d8c41ffbfe5f74e27b2aca41c29", "tree": "11c91a30e08aeee598a123b3a19145abd00ce20a", "parents": [ "b964de2119d525994285a6b365f35d08de93a57f" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:41:04 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 21:17:39 2025 +0800" }, "message": "xfs/273: fix test for internal zoned filesystems\n\nFor XFS filesystems with internal zoned sections, fsmap reports a u32\ncookie for the device instead of an actual major/minor. Adjust the test\naccordingly.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "b964de2119d525994285a6b365f35d08de93a57f", "tree": "ededdbf0435a24f733dffaa8cf03c62c60f9fdb2", "parents": [ "eb0191edd4a51981387b4aa2dcf22177543ad4b1" ], "author": { "name": "Anand Jain", "email": "anand.jain@oracle.com", "time": "Sat May 24 11:57:14 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 05:18:16 2025 +0800" }, "message": "fstests: check: fix unset seqres in run_section()\n\nWhile testing, I saw that \".full\" is created by _scratch_unmount(), called here:\n\n 725 function run_section()\n ::\n 815 if [ ! -z \"$SCRATCH_DEV\" ]; then\n 816 _scratch_unmount 2\u003e /dev/null\n 817 # call the overridden mkfs - make sure the FS is built\n\nEnsure seqres is set early in run_section() as a fix.\n\nSigned-off-by: Anand Jain \u003canand.jain@oracle.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "eb0191edd4a51981387b4aa2dcf22177543ad4b1", "tree": "da22da1f89e36f3df4a3dbce00006480317f79cb", "parents": [ "7ca990e22e0d61421d2314a81f10e2f77ac8f53a" ], "author": { "name": "Anand Jain", "email": "anand.jain@oracle.com", "time": "Sat May 24 11:57:13 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 05:18:16 2025 +0800" }, "message": "fstests: remove duplicate initialization in the testcase\n\n_begin_fstest() already initializes several variables, including `seq` and\n`seqres`, so remove those redundant initializations from the testcase.\n\nAlso, ext4/053 unnecessarily re-initializes `here`, `tmp`, and `status`,\nwhich `_begin_fstest` already handles. Remove those as well.\n\nand remove template comment.\n\nSigned-off-by: Anand Jain \u003canand.jain@oracle.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "7ca990e22e0d61421d2314a81f10e2f77ac8f53a", "tree": "7ddd2c4d940cc627d07d6918b446e10095ff88f6", "parents": [ "fa8694c823d853079775fe9cc327a595a40fe6b6" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Jun 25 17:27:35 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 05:17:44 2025 +0800" }, "message": "xfs: more multi-block atomic writes tests\n\nAdd xfs specific tests for realtime volumes and error recovery.\n\nThe first test validates multi-block atomic writes on a realtime file. We\nperform basic atomic writes operations within the advertised sizes and ensure\nthat atomic writes will fail outside of these bounds. The hardware used in this\ntest is not required to support atomic writes.\n\nThe second test verifies that a large atomic write can complete after a crash.\nThe error is injected while attempting to free an extent. We ensure that this\nerror occurs by first creating a heavily fragmented filesystem. After recovery,\nwe check that the write completes successfully.\n\nThe third test verifies that a large atomic write on a reflinked file can\ncomplete after a crash. We start with two files that share the same data and\ninject an error while attempting to perform a write on one of the files. After\nrecovery, we verify that these files now contain different data, indicating\nthat the write has succeeded.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "fa8694c823d853079775fe9cc327a595a40fe6b6", "tree": "3eaea893884801f456a8fe1c61fe055e1c23ffb8", "parents": [ "8d87273e43f1cb1bf2542697056c1f6461c399a0" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Jun 25 17:27:34 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jul 11 05:15:37 2025 +0800" }, "message": "generic: various atomic write tests with hardware and scsi_debug\n\nSimple tests of various atomic write requests and a (simulated) hardware\ndevice.\n\nThe first test performs basic multi-block atomic writes on a scsi_debug device\nwith atomic writes enabled. We test all advertised sizes between the atomic\nwrite unit min and max. We also ensure that the write fails when expected, such\nas when attempting buffered io or unaligned directio.\n\nThe second test is similar to the one above, except that it verifies multi-block\natomic writes on actual hardware instead of simulated hardware. The device used\nin this test is not required to support atomic writes.\n\nThe final two tests ensure multi-block atomic writes can be performed on various\ninterweaved mappings, including written, mapped, hole, and unwritten. We also\ntest large atomic writes on a heavily fragmented filesystem. These tests are\nseparated into reflink (shared) and non-reflink tests.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "8d87273e43f1cb1bf2542697056c1f6461c399a0", "tree": "aaa7aff60c42a68bc4ae7728dbf393a714c04027", "parents": [ "de07c1558ce0f3bb32d493ec244e19beecc93379" ], "author": { "name": "Catherine Hoang", "email": "catherine.hoang@oracle.com", "time": "Wed Jun 25 17:27:33 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jun 29 23:18:45 2025 +0800" }, "message": "common/atomicwrites: add helper for multi block atomic writes\n\nAdd a helper to check that we can perform multi block atomic writes. We will\nuse this in the following patches that add testing for large atomic writes.\nThis helper will prevent these tests from running on kernels that only support\nsingle block atomic writes.\n\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "de07c1558ce0f3bb32d493ec244e19beecc93379", "tree": "c0012ff1828dc875f9e3072d311ffa2c51d566b9", "parents": [ "a7b5d6b38296e655a9d659844937154ea57db7b8" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Thu Jun 26 08:50:21 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 27 04:07:09 2025 +0800" }, "message": "common/rc: add btrfs support for _small_fs_size_mb()\n\n[FAILURE]\nWith the incoming shutdown ioctl and remove_bdev callback support, btrfs\nis able to run the shutdown group.\n\nHowever test case like generic/042 fails on btrfs:\n\ngeneric/042 9s ... [failed, exit status 1]- output mismatch (see /home/adam/xfstests/results//generic/042.out.bad)\n --- tests/generic/042.out\t2022-05-11 11:25:30.763333331 +0930\n +++ /home/adam/xfstests/results//generic/042.out.bad\t2025-06-26 08:43:56.078509452 +0930\n @@ -1,10 +1 @@\n QA output created by 042\n -falloc -k\n -wrote 65536/65536 bytes at offset 0\n -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)\n -fpunch\n -wrote 65536/65536 bytes at offset 0\n -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/generic/042.out /home/adam/xfstests/results//generic/042.out.bad\u0027 to see the entire diff)\nRan: generic/042\nFailures: generic/042\nFailed 1 of 1 tests\n\n[CAUSE]\nThe full output shows the reason directly:\n\n ERROR: \u0027/mnt/scratch/042.img\u0027 is too small to make a usable filesystem\n ERROR: minimum size for each btrfs device is 114294784\n\nAnd the helper _small_fs_size_mb() doesn\u0027t support btrfs, thus the small\n25M file is not large enough to support a btrfs.\n\n[FIX]\nFix the false alert by adding btrfs support in _small_fs_size_mb().\n\nThe btrfs minimal size is depending on the profiles even on a single\ndevice, e.g. DUP data will cost extra space.\n\nSo here we go safe by using 512MiB as the minimal size for btrfs.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a7b5d6b38296e655a9d659844937154ea57db7b8", "tree": "fe84e61f73b7c361b26d5350cd334a777044484c", "parents": [ "e1e4a0ea3580195c1b68912cdf6db57afa168419" ], "author": { "name": "Leah Rumancik", "email": "leah.rumancik@gmail.com", "time": "Wed Jun 25 14:20:22 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 27 04:03:33 2025 +0800" }, "message": "common/rc: add repair fsck flag -f for ext4\n\nThere is a descrepancy between the fsck flags for ext4 during\nfilesystem repair and filesystem checking which causes occasional test\nfailures. In particular, _check_generic_filesystems uses -f for force\nchecking, but _repair_scratch_fs does not. In some tests, such as\ngeneric/441, we sometimes exit fsck repair early with the filesystem\nbeing deemed \"clean\" but then _check_generic_filesystems finds issues\nduring the forced full check. Bringing these flags in sync fixes the\nflakes.\n\nSigned-off-by: Leah Rumancik \u003cleah.rumancik@gmail.com\u003e\nReviewed-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e1e4a0ea3580195c1b68912cdf6db57afa168419", "tree": "10c4b93ef7370f609d0b4c0c13a35b33f7146258", "parents": [ "4b1cf3df009b225c5112eacf62250331da00273a" ], "author": { "name": "Miklos Szeredi", "email": "mszeredi@redhat.com", "time": "Mon Jun 09 17:19:15 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "overlay: add tests for data-only redirect with userxattr\n\nNew kernel feature (target release is v6.16) allows data-only redirect to\nbe enabled without metacopy and redirect_dir turned on. This works with or\nwithout verity enabled.\n\nTests are done with the userxattr option, to verify that it will work in a\nuser namespace.\n\nSigned-off-by: Miklos Szeredi \u003cmszeredi@redhat.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "4b1cf3df009b225c5112eacf62250331da00273a", "tree": "73be3983735d22f1fcda565a3aedb21a53370987", "parents": [ "8cde30495eb5199182c492c13441f7cf7f07d62f" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Mon Jun 09 17:19:14 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "fstests: add helper _require_xfs_io_shutdown\n\nRequirements for tests that shutdown fs using \"xfs_io -c shutdown\".\nThe requirements are stricter than the requirement for tests that\nshutdown fs using _scratch_shutdown helper.\n\nGenerally, with overlay fs, tests can do _scratch_shutdown, but not\nxfs_io -c shutdown.\n\nEncode this stricter requirement in helper _require_xfs_io_shutdown\nand use it in test generic/623, to express that it cannot run on\noveralyfs.\n\nReported-by: André Almeida \u003candrealmeid@igalia.com\u003e\nLink: https://lore.kernel.org/linux-fsdevel/20250521-ovl_ro-v1-1-2350b1493d94@igalia.com/\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nTested-by: André Almeida \u003candrealmeid@igalia.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "8cde30495eb5199182c492c13441f7cf7f07d62f", "tree": "f60f8fd3b756838b0d22f846c391e12cfd2c39e7", "parents": [ "d0f634afb0e30a823b044ec49fb6ea0ad0588d1c" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Mon Jun 09 17:19:13 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "fstests: add helper _scratch_shutdown_and_syncfs\n\nTest xfs/546 has to chain syncfs after shutdown and cannot\nuse the _scratch_shutdown helper, because after shutdown a fd\ncannot be opened to execute syncfs on.\n\nThe xfs_io command of chaining syncfs after shutdown is rather\nmore complex to execute in the derived overlayfs test overlay/087.\n\nAdd a helper to abstract this complexity from test writers.\nAdd a _require statement to match.\n\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d0f634afb0e30a823b044ec49fb6ea0ad0588d1c", "tree": "cb14b8214d23ce80b6a56dbd61ff8b6dd0bee5d4", "parents": [ "e17714ed95441bf2a2ee80c6e0f8af3841ffb255" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Thu Jun 19 15:30:31 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "xfs/820: skip test when metadir is not supported\n\nThe test specifically requires metadata directory functionality, so make\nit dependent on that as otherwise it fails on kernels older than v6.13\nthat do not implement the feature.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e17714ed95441bf2a2ee80c6e0f8af3841ffb255", "tree": "38b2d8c615d985e76fa94ca2f50a43b5e4d0640c", "parents": [ "2bade810290c51ab5086e5291b824d56252ac9e2" ], "author": { "name": "Daniel Gomez", "email": "da.gomez@samsung.com", "time": "Wed Jun 18 15:00:12 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "generic/551: prevent OOM when running on tmpfs with low memory\n\nRunning generic/551 on a tmpfs filesystem with less than 10 GB (ish)\nof RAM can lead to the system running out of memory, triggering the\nkernel\u0027s OOM killer and terminating the aio-dio-write-v process.\n\nFix generic/551 by substracting the amount of available memory allocated\nfor the tmpfs scratch device to the total available free memory.\n\nReported-by: Chuck Lever \u003cchuck.lever@oracle.com\u003e\nSigned-off-by: Daniel Gomez \u003cda.gomez@samsung.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "2bade810290c51ab5086e5291b824d56252ac9e2", "tree": "f40d7431636a1d440873df2f30762bc95e6131d6", "parents": [ "4230bcb1d9f66cc071b5c1de68366c1c48a4e1e3" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Fri Jun 13 14:05:08 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "btrfs/300: set umask to avoid failure on systems with a different umask\n\nThe test is assuming a umask of 0022, which is the default on many Linux\nsetups, but often we can find other umasks such as in recent Debian box\nI have where the default umask is 0002, and this makes the test fail like\nthis:\n\n $ ./check btrfs/300\n FSTYP -- btrfs\n PLATFORM -- Linux/x86_64 debian7 6.16.0-rc1-btrfs-next-200+ #1 SMP PREEMPT_DYNAMIC Thu Jun 12 16:07:55 WEST 2025\n MKFS_OPTIONS -- /dev/sdb\n MOUNT_OPTIONS -- /dev/sdb /scratch\n\n btrfs/300 2s ... - output mismatch (see /xfstests/results//btrfs/300.out.bad)\n --- tests/btrfs/300.out\t2024-05-20 11:27:55.949395116 +0100\n +++ /xfstests/results//btrfs/300.out.bad\t2025-06-12 22:58:20.449228230 +0100\n @@ -2,16 +2,16 @@\n Create subvolume \u0027./subvol\u0027\n Create subvolume \u0027subvol/subsubvol\u0027\n drwxr-xr-x fsgqa fsgqa ./\n -drwxr-xr-x fsgqa fsgqa ./subvol\n --rw-r--r-- fsgqa fsgqa ./subvol/1\n --rw-r--r-- fsgqa fsgqa ./subvol/2\n --rw-r--r-- fsgqa fsgqa ./subvol/3\n ...\n (Run \u0027diff -u /xfstests/tests/btrfs/300.out /xfstests/results//btrfs/300.out.bad\u0027 to see the entire diff)\n\n HINT: You _MAY_ be missing kernel fix:\n 94628ad94408 btrfs: copy dir permission and time when creating a stub subvolume\n\n Ran: btrfs/300\n Failures: btrfs/300\n Failed 1 of 1 tests\n\n $ diff -u /xfstests/tests/btrfs/300.out /xfstests/results//btrfs/300.out.bad\n --- /xfstests/tests/btrfs/300.out\t2024-05-20 11:27:55.949395116 +0100\n +++ /xfstests/results//btrfs/300.out.bad\t2025-06-12 22:58:20.449228230 +0100\n @@ -2,16 +2,16 @@\n Create subvolume \u0027./subvol\u0027\n Create subvolume \u0027subvol/subsubvol\u0027\n drwxr-xr-x fsgqa fsgqa ./\n -drwxr-xr-x fsgqa fsgqa ./subvol\n --rw-r--r-- fsgqa fsgqa ./subvol/1\n --rw-r--r-- fsgqa fsgqa ./subvol/2\n --rw-r--r-- fsgqa fsgqa ./subvol/3\n -drwxr-xr-x fsgqa fsgqa ./subvol/subsubvol\n --rw-r--r-- fsgqa fsgqa ./subvol/subsubvol/4\n --rw-r--r-- fsgqa fsgqa ./subvol/subsubvol/5\n --rw-r--r-- fsgqa fsgqa ./subvol/subsubvol/6\n -drwxr-xr-x fsgqa fsgqa ./snapshot\n --rw-r--r-- fsgqa fsgqa ./snapshot/1\n --rw-r--r-- fsgqa fsgqa ./snapshot/2\n --rw-r--r-- fsgqa fsgqa ./snapshot/3\n +drwxrwxr-x fsgqa fsgqa ./subvol\n +-rw-rw-r-- fsgqa fsgqa ./subvol/1\n +-rw-rw-r-- fsgqa fsgqa ./subvol/2\n +-rw-rw-r-- fsgqa fsgqa ./subvol/3\n +drwxrwxr-x fsgqa fsgqa ./subvol/subsubvol\n +-rw-rw-r-- fsgqa fsgqa ./subvol/subsubvol/4\n +-rw-rw-r-- fsgqa fsgqa ./subvol/subsubvol/5\n +-rw-rw-r-- fsgqa fsgqa ./subvol/subsubvol/6\n +drwxrwxr-x fsgqa fsgqa ./snapshot\n +-rw-rw-r-- fsgqa fsgqa ./snapshot/1\n +-rw-rw-r-- fsgqa fsgqa ./snapshot/2\n +-rw-rw-r-- fsgqa fsgqa ./snapshot/3\n drwxr-xr-x fsgqa fsgqa ./snapshot/subsubvol\n\nThe mismatch with the golden output is because the test is expecting an\numask of 0022 where the write bit is not set for owner group, but with\na umask of 0002 for example, the write bit is set for the owner group.\n\nFix this by making the test set a umask of 0022, so that it works for\nany system or user defined umask.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "4230bcb1d9f66cc071b5c1de68366c1c48a4e1e3", "tree": "358f87b3788c84a0061ae61ed27b977722963a8e", "parents": [ "ec9a19e726974bf726b75f15ab01b6ecb483d2aa" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri Jun 13 08:14:17 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "generic/740: move checking for a scratch device up\n\nCommit 3ae8a19f97d0 (\"generic/740: enable by default\") moved these checks\ndown accidentally. Move them back up to make the test exit gracefully\nwhen no scratch device is provided.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "ec9a19e726974bf726b75f15ab01b6ecb483d2aa", "tree": "5c1b1417c9a3fc7d0d590313577cabb297178eb0", "parents": [ "3893dd152f1c915d711bb24bffbc685a3ba06747" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Wed May 28 12:42:20 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "generic/032: fix failure due to attempt to wait for non-child process\n\nRunning generic/032 can sporadically fail like this:\n\n generic/032 11s ... - output mismatch (see /home/fdmanana/git/hub/xfstests/results//generic/032.out.bad)\n --- tests/generic/032.out 2023-03-02 21:47:53.884609618 +0000\n +++ /home/fdmanana/git/hub/xfstests/results//generic/032.out.bad 2025-05-28 10:39:34.549499493 +0100\n @@ -1,5 +1,6 @@\n QA output created by 032\n 100 iterations\n +/home/fdmanana/git/hub/xfstests/tests/generic/032: line 90: wait: pid 3708239 is not a child of this shell\n 000000 cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd \u003e................\u003c\n *\n 100000\n ...\n (Run \u0027diff -u /home/fdmanana/git/hub/xfstests/tests/generic/032.out /home/fdmanana/git/h\n\nThis is because we are attempting to wait for a process that is not a\nchild process of the test process and it\u0027s instead a child of a process\nspawned by the test.\n\nTo make sure that after we kill the process running _syncloop() there\nisn\u0027t any xfs_io process still running syncfs, add instead a trap to\nto _syncloop() that waits for xfs_io to finish before the process running\nthat function exits.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3893dd152f1c915d711bb24bffbc685a3ba06747", "tree": "6aedbb040596871c3fad776526fa55926f0dd091", "parents": [ "5b6072bc96a4e7948919ad4f93f6e2b970577384" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Thu Jun 12 21:05:13 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "src/fill2: fix segfault during fopen error cleanup\n\nWhen fill2 fails to open the output file (e.g. due to ENOSPC), it jumps\ninto the cleanup code where it attempts to call fclose, and this causes\na segfault within the glibc fclose code as it attempts to deref a null\npointer.\n\nFix it by conditionally calling fclose on the file pointer only when\nnon-null.\n\nThis is consistently reproducible with xfs/041.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "5b6072bc96a4e7948919ad4f93f6e2b970577384", "tree": "d10d00841e5dde28c5130747a87c487b8245cffb", "parents": [ "595773191547d36e36717ce0da4378fe726e0bc9" ], "author": { "name": "Xinjian Ma", "email": "maxj.fnst@fujitsu.com", "time": "Tue Jun 10 17:11:34 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "xfs/603: add _require_scrub\n\nThis test uses xfs_scrub which is an EXPERIMENTAL and unstable feature.\nAdd _require_scrub to check if the system supports it.\n\nSigned-off-by: Xinjian Ma \u003cmaxj.fnst@fujitsu.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "595773191547d36e36717ce0da4378fe726e0bc9", "tree": "1a2bc48253ebc68ad2349c9d53f31896d0f7ee6c", "parents": [ "a69ad67d48badc4f394c07767ad2c69fbb557b6d" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Fri Jun 13 21:52:10 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sat Jun 21 00:46:47 2025 +0800" }, "message": "generic/633: add _require_chown\n\nFor file systems that do not support chown, such as exfat,\nrunning this test does not make sense and should be skipped.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a69ad67d48badc4f394c07767ad2c69fbb557b6d", "tree": "87b2202aa3ade6eb257d845f1ce7d117eeebfd66", "parents": [ "078937463f4a5763239c7d221c168aa9cf5630b5" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Fri Jun 06 18:28:55 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 19 00:54:03 2025 +0800" }, "message": "generic/622: fix for exfat\n\nAfter commit(f761fcdd289d exfat: Implement sops-\u003eshutdown and\nioctl), shutdown is supported by exfat, this test can be run, but\nfails because exfat has a 2 second granularity for access_time\nand no timestamps for metadata changes.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "078937463f4a5763239c7d221c168aa9cf5630b5", "tree": "f315f07dacd5e9c55c5bd982a2276df542a1e35f", "parents": [ "c2acd19575e0101bee35d4b8b7b003a5e2a14f50" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Fri Jun 06 18:35:17 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Jun 18 22:42:58 2025 +0800" }, "message": "generic/689: add _require_acls\n\nBefore testing for ACLs, check whether the file system supports it\nwith _require_acls.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "c2acd19575e0101bee35d4b8b7b003a5e2a14f50", "tree": "3953a720e56fe649ff29de11b6e28af6aeed6475", "parents": [ "e7bc1e2427b4ccfd9a51a475b0d1b792b3586a40" ], "author": { "name": "Li Chen", "email": "chenl311@chinatelecom.cn", "time": "Tue Jun 10 10:52:42 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Jun 18 22:19:28 2025 +0800" }, "message": "generic/738 : add missing _fixed_by_git_commit line to the test\n\nAdd the usual _fixed_by_kernel_commit line so the user can find\nthat the hang is cured by\n\n ab23a7768739 (\"xfs: per-cpu deferred inode inactivation queues\")\n\nThe hung task call trace would be as below:\n[ 20.535519] Not tainted 5.14.0-rc4+ #27\n[ 20.537855] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 20.539420] task:738 state:D stack:14544 pid: 7124 ppid: 753 flags:0x00004002\n[ 20.540892] Call Trace:\n[ 20.541424] __schedule+0x22d/0x6c0\n[ 20.542128] schedule+0x3f/0xa0\n[ 20.542751] percpu_rwsem_wait+0x100/0x130\n[ 20.543516] ? percpu_free_rwsem+0x30/0x30\n[ 20.544259] __percpu_down_read+0x44/0x50\n[ 20.545002] xfs_trans_alloc+0x19a/0x1f0\n[ 20.545747] xfs_free_eofblocks+0x47/0x100\n[ 20.546519] xfs_inode_mark_reclaimable+0x115/0x160\n[ 20.547398] destroy_inode+0x36/0x70\n[ 20.548077] prune_icache_sb+0x79/0xb0\n[ 20.548789] super_cache_scan+0x159/0x1e0\n[ 20.549536] shrink_slab.constprop.0+0x1b1/0x370\n[ 20.550363] drop_slab_node+0x1d/0x40\n[ 20.551041] drop_slab+0x30/0x70\n[ 20.551600] drop_caches_sysctl_handler+0x6b/0x80\n[ 20.552311] proc_sys_call_handler+0x12b/0x250\n[ 20.552931] new_sync_write+0x117/0x1b0\n[ 20.553462] vfs_write+0x1bd/0x250\n[ 20.553914] ksys_write+0x5a/0xd0\n[ 20.554381] do_syscall_64+0x3b/0x90\n[ 20.554854] entry_SYSCALL_64_after_hwframe+0x44/0xae\n[ 20.555481] RIP: 0033:0x7f90928d3300\n[ 20.555946] RSP: 002b:00007ffc2b50b998 EFLAGS: 00000202 ORIG_RAX: 0000000000000001\n[ 20.556853] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f90928d3300\n[ 20.557686] RDX: 0000000000000002 RSI: 000055a5d6c47750 RDI: 0000000000000001\n[ 20.558524] RBP: 000055a5d6c47750 R08: 0000000000000007 R09: 0000000000000073\n[ 20.559335] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002\n[ 20.560154] R13: 00007f90929ae760 R14: 0000000000000002 R15: 00007f90929a99e0\n\nlocalhost login: [ 30.773559] INFO: task 738:7124 blocked for more than 20 seconds.\n[ 30.775236] Not tainted 5.14.0-rc4+ #27\n[ 30.777449] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 30.779729] task:738 state:D stack:14544 pid: 7124 ppid: 753 flags:0x00004002\n[ 30.781267] Call Trace:\n[ 30.781850] __schedule+0x22d/0x6c0\n[ 30.782618] schedule+0x3f/0xa0\n[ 30.783297] percpu_rwsem_wait+0x100/0x130\n[ 30.784110] ? percpu_free_rwsem+0x30/0x30\n[ 30.785085] __percpu_down_read+0x44/0x50\n[ 30.786071] xfs_trans_alloc+0x19a/0x1f0\n[ 30.786877] xfs_free_eofblocks+0x47/0x100\n[ 30.787727] xfs_inode_mark_reclaimable+0x115/0x160\n[ 30.788708] destroy_inode+0x36/0x70\n[ 30.789395] prune_icache_sb+0x79/0xb0\n[ 30.790056] super_cache_scan+0x159/0x1e0\n[ 30.790712] shrink_slab.constprop.0+0x1b1/0x370\n[ 30.791381] drop_slab_node+0x1d/0x40\n[ 30.791924] drop_slab+0x30/0x70\n[ 30.792469] drop_caches_sysctl_handler+0x6b/0x80\n[ 30.793328] proc_sys_call_handler+0x12b/0x250\n[ 30.793948] new_sync_write+0x117/0x1b0\n[ 30.794471] vfs_write+0x1bd/0x250\n[ 30.794941] ksys_write+0x5a/0xd0\n[ 30.795414] do_syscall_64+0x3b/0x90\n[ 30.795928] entry_SYSCALL_64_after_hwframe+0x44/0xae\n[ 30.796595] RIP: 0033:0x7f90928d3300\n[ 30.797090] RSP: 002b:00007ffc2b50b998 EFLAGS: 00000202 ORIG_RAX: 0000000000000001\n[ 30.798033] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f90928d3300\n[ 30.798852] RDX: 0000000000000002 RSI: 000055a5d6c47750 RDI: 0000000000000001\n[ 30.799703] RBP: 000055a5d6c47750 R08: 0000000000000007 R09: 0000000000000073\n[ 30.800833] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002\n[ 30.801764] R13: 00007f90929ae760 R14: 0000000000000002 R15: 00007f90929a99e0\n[ 30.802628] INFO: task xfs_io:7130 blocked for more than 10 seconds.\n[ 30.803421] Not tainted 5.14.0-rc4+ #27\n[ 30.803985] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 30.804979] task:xfs_io state:D stack:13712 pid: 7130 ppid: 7127 flags:0x00000002\n[ 30.806013] Call Trace:\n[ 30.806399] __schedule+0x22d/0x6c0\n[ 30.806867] schedule+0x3f/0xa0\n[ 30.807334] rwsem_down_write_slowpath+0x1d8/0x510\n[ 30.808018] thaw_super+0xd/0x20\n[ 30.808748] __x64_sys_ioctl+0x5d/0xb0\n[ 30.809292] do_syscall_64+0x3b/0x90\n[ 30.809797] entry_SYSCALL_64_after_hwframe+0x44/0xae\n[ 30.810454] RIP: 0033:0x7ff1b48c5d1b\n[ 30.810943] RSP: 002b:00007fff0bf88ac0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\n[ 30.811874] RAX: ffffffffffffffda RBX: 000055b93ae5fc40 RCX: 00007ff1b48c5d1b\n[ 30.812743] RDX: 00007fff0bf88b2c RSI: ffffffffc0045878 RDI: 0000000000000003\n[ 30.813583] RBP: 000055b93ae60fe0 R08: 0000000000000000 R09: 0000000000000000\n[ 30.814497] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001\n[ 30.815413] R13: 000055b93a3a94e9 R14: 0000000000000000 R15: 000055b93ae61150\n\nSigned-off-by: Li Chen \u003cchenl311@chinatelecom.cn\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e7bc1e2427b4ccfd9a51a475b0d1b792b3586a40", "tree": "50c5461a4937ac1d482629365a3d7e1b96da87dc", "parents": [ "e225772353e212c3b321a31c6ddb364684378e8e" ], "author": { "name": "Hans Holmberg", "email": "Hans.Holmberg@wdc.com", "time": "Mon Jun 09 11:03:54 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Jun 18 22:16:07 2025 +0800" }, "message": "ext4/002: make generic to support xfs\n\nxfs supports separate log devices and as this test now passes, share\nit by turning it into a generic test.\n\nThis should not result in a new failure for other file systems as only\next2/ext3/ext4 and xfs supports mkfs with SCRATCH_LOGDEVs.\n\nSigned-off-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e225772353e212c3b321a31c6ddb364684378e8e", "tree": "2fe8426c7a28495131329e28bcb2b25eebeb6ef8", "parents": [ "b3da4865e80d920158906b7a138081f8921545c6" ], "author": { "name": "Hans Holmberg", "email": "Hans.Holmberg@wdc.com", "time": "Mon Jun 09 11:03:53 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Jun 18 22:16:07 2025 +0800" }, "message": "xfs: add mount test for read only rt devices\n\nMake sure that we can mount rt devices read-only if them themselves\nare marked as read-only.\n\nAlso make sure that rw re-mounts are not allowed if the device is\nmarked as read-only.\n\nBased on generic/050.\n\nSigned-off-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "b3da4865e80d920158906b7a138081f8921545c6", "tree": "a6d352896e7d42209755c83820d45fd448bab7dc", "parents": [ "3563fda0140f8512e15578eb975da15d0fa04052" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Thu Jun 05 09:25:24 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jun 08 21:48:09 2025 +0800" }, "message": "fstests: generic/741: make cleanup to handle test failure properly\n\n[BUG]\nWhen I was tinkering the bdev open holder parameter, it caused a bug\nthat it no longer rejects mounting the underlying device of a\ndevice-mapper.\n\nAnd the test case properly detects the regression:\n\ngeneric/741 1s ... umount: /mnt/test: target is busy.\n_check_btrfs_filesystem: filesystem on /dev/mapper/test-test is inconsistent\n(see /home/adam/xfstests/results//generic/741.full for details)\nTrying to repair broken TEST_DEV file system\n_check_btrfs_filesystem: filesystem on /dev/mapper/test-scratch1 is inconsistent\n(see /home/adam/xfstests/results//generic/741.full for details)\n- output mismatch (see /home/adam/xfstests/results//generic/741.out.bad)\n --- tests/generic/741.out\t2024-04-06 08:10:44.773333344 +1030\n +++ /home/adam/xfstests/results//generic/741.out.bad\t2025-06-05 09:18:03.675049206 +0930\n @@ -1,3 +1,2 @@\n QA output created by 741\n -mount: TEST_DIR/extra_mnt: SCRATCH_DEV already mounted or mount point busy\n -mount: TEST_DIR/extra_mnt: SCRATCH_DEV already mounted or mount point busy\n +rm: cannot remove \u0027/mnt/test/extra_mnt\u0027: Device or resource busy\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/generic/741.out /home/adam/xfstests/results//generic/741.out.bad\u0027 to see the entire diff)\n\nThe problem is, all later test will fail, because the $SCRATCH_DEV is\nstill mounted at $extra_mnt:\n\n TEST_DEV\u003d/dev/mapper/test-test is mounted but not on TEST_DIR\u003d/mnt/test - aborting\n Already mounted result:\n /dev/mapper/test-test /mnt/test /dev/mapper/test-test /mnt/test\n\n[CAUSE]\nThe test case itself is doing two expected-to-fail mounts, but the\ncleanup function is only doing unmount once, if the mount succeeded\nunexpectedly, the $SCRATCH_DEV will be mounted at $extra_mnt forever.\n\n[ENHANCEMENT]\nTo avoid screwing up later test cases, do the $extra_mnt cleanup twice\nto handle the unexpected mount success.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3563fda0140f8512e15578eb975da15d0fa04052", "tree": "6a5af470f2ccf86d1e2e55f435682ef2a56f32a4", "parents": [ "3d339199525f1a74a08210701c117dc2731286d6" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Tue Jun 03 12:07:45 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 19:45:46 2025 +0800" }, "message": "generic/699: fix failure with MOUNT_OPTIONS\n\ngeneric/699 uses overalyfs helper _overlay_mount_dirs, which is meant to\nbe used by overlayfs tests, where MOUNT_OPTIONS refer to overalyfs mount\noptions.\n\nUsing this helper from a generic test when FSTYP is not overlay is\ncausing undesired results. For example, when MOUNT_OPTIONS is defined\nand includes a mount option not supported by overalyfs (e.g. \u0027acl\u0027),\nthe test is notrun because of:\n\nmount: /vdc/ovl-merge: fsconfig() failed: overlay: Unknown parameter \u0027acl\u0027.\n\nThere is no other generic test that includes the common/overlay helpers\nand uses them, so remove this practice from generic/699 as well.\n\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3d339199525f1a74a08210701c117dc2731286d6", "tree": "fd334474790b70509e4f17853b93fff70597d512", "parents": [ "3b385bf1e90f9d59213b4c198cabe2480d9ca9ef" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Mon May 26 19:54:37 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 19:45:46 2025 +0800" }, "message": "generic: remove incorrect _require_idmapped_mounts checks\n\ncommit f5661920 (\"generic: add missed _require_idmapped_mounts check\")\nwrongly adds _require_idmapped_mounts to tests that do not require\nidmapped mounts support.\n\nThe added _require_idmapped_mounts in test generic/633 goes against\ncommit d8dee122 (\"idmapped-mounts: always run generic vfs tests\")\nthat intentionally removed this requirement from the generic tests.\n\nThe added _require_idmapped_mounts in tests generic/69{6,7} causes\nthose tests not to run with overlayfs, which does not support idmapped\nmounts. However, those tests are regression tests to kernel commit\n1639a49ccdce (\"fs: move S_ISGID stripping into the vfs_*() helpers\")\nwhich is documented as also solving a correction issue with overlayfs,\nso removing this test converage is very much undesired.\n\nRemove the incorrectly added _require_idmapped_mounts checks.\nAlso fix the log in _require_idmapped_mounts to say that\n\"idmapped mounts not support by $FSTYP\", which is what the helper\nchecks instead of \"vfstests not support by $FSTYP\" which is incorrect.\n\nCc: Yang Xu \u003cxuyang2018.jy@fujitsu.com\u003e\nCc: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nCc: David Disseldorp \u003cddiss@suse.de\u003e\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Christian Brauner \u003cbrauner@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3b385bf1e90f9d59213b4c198cabe2480d9ca9ef", "tree": "730be57a6b0167927b719e5c6b9f7f8e846ef859", "parents": [ "d235c7eef1d84b2ba5502cb866efca0f16e437dc" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Tue Jun 03 12:07:42 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 19:45:46 2025 +0800" }, "message": "generic/604: do not run with overlayfs\n\nOverlayfs does not allow mounting over again with the same layers\nuntil umount is fully completed, so is not appropriate for this test\nwhich tries to mount in parallel to umount.\n\nThis is manifested as the test failure below when overlayfs strict mount\nchecks are enabled by enabling the index feature:\n\n$ echo Y \u003e /sys/module/overlay/parameters/index\n...\n +mount: /vdf/ovl-mnt: /vdf already mounted or mount point busy.\n + dmesg(1) may have more information after failed mount system call.\n +mount /vdf /vdf/ovl-mnt failed\n\nOpt-out of this test with overlayfs and remove the hacks that were placed\nby commit 06cee932 (\"generic/604: Fix for overlayfs\") to make the test pass\nwith overlayfs in the first place.\n\nTested-by: André Almeida \u003candrealmeid@igalia.com\u003e\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d235c7eef1d84b2ba5502cb866efca0f16e437dc", "tree": "067509ca22adc6a353f8e017b9b2f9b58369193d", "parents": [ "e6fc42f16c77ea40090b7168a7195ea12967b012" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Tue Jun 03 12:07:41 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 19:45:46 2025 +0800" }, "message": "overlay: fix regression in _repair_overlay_scratch_fs\n\n_repair_overlay_scratch_fs assumed that the base fs is mounted.\nThis was a wrong assumption to make, and that was exposed by commit\n4c6bc456 (\"fstests: clean up mount and unmount operations\") that\nconverted open coded umount in generic/332 to _scratch_unmount.\n\nAfter this change, there errors were observed when running generic/332\nif fsck.overlay is installed:\n\n Check for damage\n +fsck.overlay:[Error]: Faile to resolve upperdir:/vdf/ovl-upper:\n No such file or directory\n +fsck.overlay failed, err\u003d8\n +umount: /vdf: not mounted.\n\nFix this by making sure that base fs is mounted before running the\nlayers check and fix test generic/330 to conform with the umount\nconversion patch.\n\nFixes: 4c6bc456 (\"fstests: clean up mount and unmount operations\")\nTested-by: André Almeida \u003candrealmeid@igalia.com\u003e\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e6fc42f16c77ea40090b7168a7195ea12967b012", "tree": "84d66f759c5e05b1190bd9183c5d7d57af833a5e", "parents": [ "2f635d075e104e69d58dc48c88697c64181a22b6" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Tue Jun 03 12:07:40 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 19:45:46 2025 +0800" }, "message": "overlay: workaround libmount failure to remount,ro\n\nlibmount \u003e\u003d v1.39 calls several unneeded fsconfig() calls to reconfigure\nlowerdir/upperdir when user requests only -o remount,ro.\n\nThose calls fail because overlayfs does not allow making any config\nchanges with new mount api, besides MS_RDONLY.\n\nWe workaround this problem with --options-mode ignore.\n\nReported-by: André Almeida \u003candrealmeid@igalia.com\u003e\nSuggested-by: Karel Zak \u003ckzak@redhat.com\u003e\nLink: https://lore.kernel.org/linux-fsdevel/20250521-ovl_ro-v1-1-2350b1493d94@igalia.com/\nLink: https://lore.kernel.org/fstests/CAJfpegtJ3SDKmC80B4AfWiC3JmtWdW2+78fRZVtsuhe-wSRPvg@mail.gmail.com/\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "2f635d075e104e69d58dc48c88697c64181a22b6", "tree": "4d999dd1f18b89bd21761b0bd6b3dc962158cb13", "parents": [ "09ab269c0419fd1e8c927c09b507244db0c15cd5" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Fri May 23 18:20:50 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "fsstress: print syncfs() return value in verbose mode\n\nWe aren\u0027t logging the syncfs() return value in case we are running in\nverbose mode, which is useful and it would help me immediately figuring\nout it was failing in a problem I was debugging with btrfs.\n\nSo log its return value, just like we do for every other fsstress command.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "09ab269c0419fd1e8c927c09b507244db0c15cd5", "tree": "6ddae6728711b1ab5c52d374d99ea81cb4f49e62", "parents": [ "389d34f0ab02c34115b9c5292dc1efd3be10a8e2" ], "author": { "name": "Chunhai Guo", "email": "guochunhai@vivo.com", "time": "Mon May 26 02:03:23 2025 -0600" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "f2fs/014: test for missing \u0027trimmed\u0027 flag issue\n\nThis is a regression test case to verify whether the CP_TRIMMED_FLAG is\nproperly set after performing the following steps:\n1. mount the f2fs filesystem\n2. create a file, write data to it, then delete the file\n3. unmount the filesystem\n4. verify that the \u0027trimmed\u0027 flag is set in the checkpoint state\n\nWe should apply the commit (\"f2fs: fix missing discard for active\nsegments\") to resolve the issue where the \u0027trimmed\u0027 flag is missing.\n\nSigned-off-by: Chunhai Guo \u003cguochunhai@vivo.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "389d34f0ab02c34115b9c5292dc1efd3be10a8e2", "tree": "a2dccf355aa6bfcb9be905ad42b17f01ad6c4043", "parents": [ "5ca2b3450351ca504e829cc57bdd16c715496fd4" ], "author": { "name": "Jan Prusakowski", "email": "jprusakowski@google.com", "time": "Fri May 30 09:23:49 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "f2fs/004: avoid race condition in test\n\nIn current implementation the atomic write may not start before\nthe direct write and the test fails.\n\nThe patch adds a delay after starting the atomic write process\nso it has a chance to actually start wrtiting data and set the\ninternal state of the file correctly.\n\nSigned-off-by: Jan Prusakowski \u003cjprusakowski@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "5ca2b3450351ca504e829cc57bdd16c715496fd4", "tree": "efcc6e8c925cfdbb221ee35fa7b0bc2624e5714a", "parents": [ "d866af976999cdcc3c548b4bf5baa865942e895f" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu May 29 12:33:13 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/094: fix test ignoring failures\n\nThe test is ignoring failures completely:\n\n1) If mounting the scratch device fails it redirects both stdout and\n stderr to /dev/null, so it gets unnoticed and the test runs against\n a different fs than expected (in my test environment $SCRATCH_MNT\n points to a directory in an ext4 fs for example but I want to test\n btrfs);\n\n2) We are redirecting the stdout and stderr of fiemap-tester to the\n $seqres.full file, so if it fails it gets completely unnoticed and\n the test succeeds.\n\nFor the first issue fix this by not even using the scratch filesystem and\nuse instead the test filesystem, since the test creates a 2M file which\nis small enough.\n\nFor the second issue simply don\u0027t redirect the stdout and stderr, so that\nif the test program fails it causes a mismatch with the golden output,\nmaking the test fail.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d866af976999cdcc3c548b4bf5baa865942e895f", "tree": "65466b62ff62ae0f5ff4f3fa2e4888263e07e17d", "parents": [ "a75c1aae9f930c9bd9a442dc256438627405662f" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu May 29 12:13:41 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "fstests: add kernel commit IDs to some tests\n\nThe kernel fixes exercised by some tests have already landed in Linus\u0027\ntree, so update the tests with the respective commit IDs.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a75c1aae9f930c9bd9a442dc256438627405662f", "tree": "18cfdceebe26021686631f1a1f59e458d4536412", "parents": [ "68c9ac2ad74ba31c02275fcbb11d1cf90f0435b1" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:29 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/645: add _require_chown\n\nThis test uses chown to set GID and UID, which requires chown\nsupport, so add _require_chown to check for chown support.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "68c9ac2ad74ba31c02275fcbb11d1cf90f0435b1", "tree": "fb2669a312e1acfbf19cb3ac3ce10fe248ce4851", "parents": [ "bb77b42ba80f8f3e5f8523c8bb80cb3e6ae9ca55" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:28 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/730: add _require_scratch_shutdown\n\nBefore testing for shutdown, check whether the file system\nsupports it with _require_scratch_shutdown.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "bb77b42ba80f8f3e5f8523c8bb80cb3e6ae9ca55", "tree": "ed35157b2ccda1a6fe3b7316faca7f43ae89473d", "parents": [ "2f14ca462c65f08dbe66dde13e7510eaed2e6c64" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:27 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/755: add _require_hardlinks\n\nThis test is used to test whether the ctime of the original file\nchanges after deleting its hard link, which requires hardlink\nsupport, so add _require_hardlinks to check for hardlink support.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "2f14ca462c65f08dbe66dde13e7510eaed2e6c64", "tree": "37ba6d81c3354267cf694d710ca2a4ecdcb36873", "parents": [ "2d9dac4ef7639aae53b6aea47761bf6be2cf0658" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:26 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/754: add _require_symlinks\n\nThis test tests whether xattrs can be added to a symbolic link,\nwhich requires symlink support, so add _require_symlinks to check\nfor symlink support.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "2d9dac4ef7639aae53b6aea47761bf6be2cf0658", "tree": "dfa3172c2682d40ad9bc1a05f649b6e612edfd64", "parents": [ "4b12c46aa728946b3a5badfc7355c627fc8c1fdc" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:25 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/656: add _require_chown\n\nThis test uses chown to set GID and UID, which requires chown\nsupport, so add _require_chown to check for chown support.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "4b12c46aa728946b3a5badfc7355c627fc8c1fdc", "tree": "67c3fd442cd6b876cc1887bbf88d31f5eb79477a", "parents": [ "4f2e4be4a632369e0015026f1965264904a085bf" ], "author": { "name": "Yuezhang Mo", "email": "Yuezhang.Mo@sony.com", "time": "Wed May 28 17:15:24 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Jun 06 09:55:44 2025 +0800" }, "message": "generic/696: add _require_chmod\n\nThis test uses chmod to set the S_ISGID bit, which requires chmod\nsupport, so add _require_chmod to check for chmod support.\n\nSigned-off-by: Yuezhang Mo \u003cYuezhang.Mo@sony.com\u003e\nReviewed-by: Friendy Su \u003cfriendy.su@sony.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "4f2e4be4a632369e0015026f1965264904a085bf", "tree": "49e28a3995e135b5e5b41a705cbf54f84d7b2018", "parents": [ "fce21ab7afff4518e6663e37fd22268c3f8f07a5" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jun 02 12:22:14 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 05 21:48:26 2025 +0800" }, "message": "common/atomicwrites: fix _require_scratch_write_atomic\n\nFix this function to call _notrun whenever something fails. If we can\u0027t\nfigure out the atomic write geometry, then we haven\u0027t satisfied the\npreconditions for the test.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "fce21ab7afff4518e6663e37fd22268c3f8f07a5", "tree": "4a3448b5f7c2b9f56822a7258723fae177f3649c", "parents": [ "909ee4c8a75b28e012581122f935e160eef6b6bd" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jun 02 12:22:13 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 05 21:48:26 2025 +0800" }, "message": "common/atomicwrites: adjust a few more things\n\nAlways export STATX_WRITE_ATOMIC so anyone can use it, make the \"cp\nreflink\" logic work for any filesystem, not just xfs, and create a\nseparate helper to check that the necessary xfs_io support is present.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "909ee4c8a75b28e012581122f935e160eef6b6bd", "tree": "9d9428d93aae4a598645d6df97f783f2fad958ac", "parents": [ "01b46074f237a9792eafa2eb797f7918da5a2360" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jun 02 12:22:12 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 05 21:48:26 2025 +0800" }, "message": "generic/765: move common atomic write code to a library file\n\nMove the common atomic writes code to common/atomicwrites so we can share\nthem.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "01b46074f237a9792eafa2eb797f7918da5a2360", "tree": "618d49804eb717c89a423ed1943b2dde81cb9316", "parents": [ "b9666a70cb85e1a9d9a4d938e7458116f4567e14" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jun 02 12:22:11 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 05 21:48:26 2025 +0800" }, "message": "generic/765: adjust various things\n\nFix some bugs when detecting the atomic write geometry, record what\natomic write geometry we\u0027re testing each time through the loop, and\ncreate a group for atomic writes tests.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "b9666a70cb85e1a9d9a4d938e7458116f4567e14", "tree": "8eb709f474755e1bccd3a3ebc81386f11c6c7a0c", "parents": [ "b7680adf9ff7bdc962fb95b5cbd304abd3137b69" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jun 02 12:22:10 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jun 05 21:48:26 2025 +0800" }, "message": "generic/765: fix a few issues\n\nFix a few bugs in the single block atomic writes test, such as not requiring\ndirectio, using the page size for the ext4 max bsize, and making sure we check\nthe max atomic write size.\n\nCc: ritesh.list@gmail.com\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: John Garry \u003cjohn.g.garry@oracle.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "b7680adf9ff7bdc962fb95b5cbd304abd3137b69", "tree": "130679ec55c5b04a216ce9c11b18558f778a1d71", "parents": [ "67b823d4a832bdc79e1750774d67f0841413b312" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Fri May 09 19:04:56 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun May 25 19:56:12 2025 +0800" }, "message": "open_by_handle: add a test for connectable file handles\n\nThis is a variant of generic/477 with connectable file handles.\nThis test uses load and store of file handles from a temp file to test\ndecoding connectable file handles after cycle mount and after renames.\n\nDecoding connectable file handles after being moved to a new parent\nis expected to fail on some filesystems, but not on filesystems that\ndo not really get unmounted in mount cycle like tmpfs, so skip this test.\n\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "67b823d4a832bdc79e1750774d67f0841413b312", "tree": "205f468dd86f7d8a758011003913f106ecf7a480", "parents": [ "22cc9e29bdf8ead5aeac4bdfa37572ae56add16c" ], "author": { "name": "Amir Goldstein", "email": "amir73il@gmail.com", "time": "Fri May 09 19:00:32 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun May 25 19:55:27 2025 +0800" }, "message": "open_by_handle: add support for testing connectable file handles\n\nTest for kernel and filesystem support for conenctable file handles.\n\nWith -N flag, encode connectable file handles and fail the test if the\nkernel or filesystem do not support conenctable file handles.\n\nVerify that decoding connectable file handles always results in a non\nempty path of the fd.\n\nSigned-off-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "22cc9e29bdf8ead5aeac4bdfa37572ae56add16c", "tree": "2c0dca8804a5f084bbf10476380f9b52b482fc77", "parents": [ "49170253afef82a3a4adf5db086733bd853b45db" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Wed May 14 08:33:01 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:39:02 2025 +0800" }, "message": "fstests: btrfs/020: use device pool to avoid busy TEST_DEV\n\n[BUG]\nThere is an internal report about btrfs/020 failure, the 020.full looks\nlike this:\n\n ERROR: ioctl(DEV_REPLACE_START) failed on \"/opt/test/020.5968.mnt\": Read-only file system\n\n Performing full device TRIM /dev/loop8 (256.00MiB) ...\n _check_btrfs_filesystem: filesystem on /dev/loop0 is inconsistent\n *** fsck.btrfs output ***\n ERROR: /dev/loop0 is currently mounted, use --force if you really intend to check the filesystem\n Opening filesystem to check...\n *** end fsck.btrfs output\n *** mount output ***\n [...]\n /dev/loop0 on /opt/test type btrfs (rw,relatime,seclabel,ssd,discard\u003dasync,space_cache\u003dv2,subvolid\u003d5,subvol\u003d/)\n *** end mount output\n\n[CAUSE]\nUnfortunately I can not reproduce the situation here, but it looks like\nby somehow we didn\u0027t unmount the TEST_DEV before checking it.\n\nThis may or may not be caused by the fact we\u0027re using loop back devices\non TEST_MNT.\n\n[FIX]\nFor this particluar test case, we really do not need to use TEST_MNT and\ncreate complex loopback devices.\n\nWe can just ask for 3 devices from the device pool, use 2 for the raid1\nfs, and then use the spare one for dev replace.\n\nThis should greately simplify the test case setup and cleanup, thus\navoid the above busy TEST_DEV and false test failure.\n\nFurthermore use the golden output to match the error message, and since\nwe\u0027re here also handle a bug in btrfs-progs where the error message is\nincorrectly split into two lines.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Anand Jain \u003canand.jain@oracle.com\u003e\n" }, { "commit": "49170253afef82a3a4adf5db086733bd853b45db", "tree": "2008c55c623ad12ebc297e46c1d0d9e37dcb6fb2", "parents": [ "1e1d98c85d733cfd622f19d663ec9ee2c16da239" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue May 13 16:37:49 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:39:02 2025 +0800" }, "message": "fstests: btrfs/220: do not use nologreplay when possible\n\n[BUG]\nIf the system is using mount from util-linux 2.41 or newer, the test\ncase will fail with the following error:\n\n FSTYP -- btrfs\n PLATFORM -- Linux/x86_64 btrfs-vm 6.15.0-rc5-custom+ #238 SMP PREEMPT_DYNAMIC Wed May 7 14:10:51 ACST 2025\n MKFS_OPTIONS -- /dev/mapper/test-scratch1\n MOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\n btrfs/220 6s ... - output mismatch (see /home/adam/xfstests/results//btrfs/220.out.bad)\n --- tests/btrfs/220.out\t2022-05-11 11:25:30.749999997 +0930\n +++ /home/adam/xfstests/results//btrfs/220.out.bad\t2025-05-13 16:26:18.068521503 +0930\n @@ -1,2 +1,4 @@\n QA output created by 220\n +mount warning:\n + * btrfs: Deprecated parameter \u0027nologreplay\u0027\n Silence is golden\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/btrfs/220.out /home/adam/xfstests/results//btrfs/220.out.bad\u0027 to see the entire diff)\n Ran: btrfs/220\n Failures: btrfs/220\n Failed 1 of 1 tests\n\n[CAUSE]\nThe newer mount command provides the extra ability to show warning during\nmount.\n\nAlthough btrfs still supports \"nologreplay\" mount option to keep\nconsistency with other filesystems, we will output a warning and\nencourage users to use \"rescue\u003dnologreplay\" instead.\n\nDuring \"nologreplay\" mount option test, normally we will mount use\nthe newer \"rescue\u003dnologreplay\" mount option if the kernel supports.\n\nBut the following two call sites are still unconditionally utilizing\nthe deprecated \"nologreplay\" mount option directly:\n\n- Expected failure when using nologreplay and rw mount\n\n- Mount option verification that \"nologreplay\" is converted to\n \"rescue\u003dnologreplay\"\n\nThe second call site caused the above mount warning message and fail the\ntest case.\n\n[FIX]\nIf the kernel supports \"rescue\u003dnologreplay\" we should not utilized\n\"nologreplay\" at all.\n\nThis will avoid the mount warning on the deprecated and discouraged\n\"nologreplay\" mount option.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Anand Jain \u003canand.jain@oracle.com\u003e\n" }, { "commit": "1e1d98c85d733cfd622f19d663ec9ee2c16da239", "tree": "e233eedeef6e724ba764a36d4575d128deef88b5", "parents": [ "3bbdf4241a5f4c7c0b02dad7617c29a053e2a24a" ], "author": { "name": "Johannes Thumshirn", "email": "johannes.thumshirn@wdc.com", "time": "Mon May 12 08:07:49 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:39:02 2025 +0800" }, "message": "fstests: btrfs: add git commit ID to btrfs/335\n\nNow that kernel commit \u0027b0c26f479926 (\"btrfs: zoned: return EIO on RAID1 block\ngroup write pointer mismatch\")\u0027 is merged, add git commit ID to fstests\nbtrfs/335 and also add the test to the auto group.\n\nSigned-off-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3bbdf4241a5f4c7c0b02dad7617c29a053e2a24a", "tree": "fd650d9eb2dacb2bb69f9297ae666c45f64ba8e3", "parents": [ "282e4fe8cf47693a45206bcf7c5957c83cb1043a" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Mon May 12 19:09:10 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:39:02 2025 +0800" }, "message": "fstests: btrfs: a new test case to verify scrub and rescue\u003didatacsums\n\nThere is a kernel bug report that scrub will trigger a NULL pointer\ndereference when rescue\u003didatacsums mount option is provided.\n\nAdd a test case for such situation, to verify kernel can gracefully\nreject scrub when there is no csum tree.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "282e4fe8cf47693a45206bcf7c5957c83cb1043a", "tree": "2ade9ed41553597b8d1353c371147259d46da5aa", "parents": [ "3c21ae673e70cc94bb23a95994daec442c26a331" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu May 15 12:50:08 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:39:02 2025 +0800" }, "message": "btrfs/023: add to the quick group\n\nThis is a very quick test, so add it to the quick group.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "3c21ae673e70cc94bb23a95994daec442c26a331", "tree": "7c5e87caa0e2516e7d1041dfaf1a9860b9e0c04f", "parents": [ "7e41a4a04bdfd42798aba9a048027abc717c1817" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu May 15 12:50:07 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:23:41 2025 +0800" }, "message": "btrfs: add tests that exercise raid profiles to the raid group\n\nMany tests (in fact most) that exercise one or more raid profiles are not\ntagged in the raid group. Tag them with the raid group so that we can\neasily run only raid test with \"./check -g raid\" when testing changes that\naffect only raid code.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "7e41a4a04bdfd42798aba9a048027abc717c1817", "tree": "8cb2e664dd71bf5cd95d6f1d8afdb9a0e967edcf", "parents": [ "359cb24a11d846e3e83f99743ed8ca02646e501e" ], "author": { "name": "Nirjhar Roy (IBM)", "email": "nirjhar.roy.lists@gmail.com", "time": "Thu May 22 05:41:35 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:16:05 2025 +0800" }, "message": "new: Replace \"status\u003d0; exit 0\" with _exit 0\n\nWe should now start using _exit 0 for every new test\nthat we add.\n\nSigned-off-by: Nirjhar Roy (IBM) \u003cnirjhar.roy.lists@gmail.com\u003e\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "359cb24a11d846e3e83f99743ed8ca02646e501e", "tree": "5b7adc17c31766fe46475f7ba963671b47f7b927", "parents": [ "75372b7617a2e6c3f150eaa0d925b177a6966314" ], "author": { "name": "Nirjhar Roy (IBM)", "email": "nirjhar.roy.lists@gmail.com", "time": "Thu May 22 05:41:34 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 23:16:05 2025 +0800" }, "message": "new: Add a new parameter (copyright-owner) in the \"new\" script\n\nThis patch another optional interactive prompt to enter the\ncopyright-owner for each new test file that is created using\nthe \"new\" file.\n\nThe sample output looks like something like the following:\n\n./new selftest\nNext test id is 007\nAppend a name to the ID? Test name will be 007-$name. y,[n]:\nCreating test file \u0027007\u0027\nAdd to group(s) [auto] (separate by space, ? for list): selftest quick\nEnter \u003ccopyright owner\u003e: IBM Corporation\nCreating skeletal script for you to edit ...\n done.\n\nSigned-off-by: Nirjhar Roy (IBM) \u003cnirjhar.roy.lists@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "75372b7617a2e6c3f150eaa0d925b177a6966314", "tree": "fe79ec0fd180d35cb4540f97284a5437709848cd", "parents": [ "68fa350e1e776b6179cda4847c9f68070d2251c9" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Fri May 09 14:07:54 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 21:53:18 2025 +0800" }, "message": "f2fs/013: test to check potential corruption on atomic_write file\n\nThis is a regression testcase to check whether we will handle database\ninode dirty status correctly:\n1. mount f2fs image w/ timeout fault injection option\n2. create a regular file, and write data into the file\n3. start transaction on the file (via F2FS_IOC_START_ATOMIC_WRITE)\n4. write transaction data to the file\n5. commit and end the transaction (via F2FS_IOC_COMMIT_ATOMIC_WRITE)\n6. meanwhile loop call fsync in parallel\nBefore f098aeba04c9 (\"f2fs: fix to avoid atomicity corruption of atomic\nfile\"), database file may become corrupted after atomic write while\nthere is concurrent dirty inode flush in background.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Daeho Jeong \u003cdaehojeong@google.com\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "68fa350e1e776b6179cda4847c9f68070d2251c9", "tree": "bfe4412a2ace4023a435f23892d2e45ca5334888", "parents": [ "cc0dcbf488495efea9575785ae8566280f232e58" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:42:54 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 21:43:29 2025 +0800" }, "message": "check: check and fix the test filesystem after failed tests\n\nCurrently, ./check calls _check_filesystems after a test passes to make\nsure that the test and scratch filesystems are ok, and repairs the test\nfilesystem if it\u0027s not ok.\n\nHowever, we don\u0027t do this for failed tests. If a test fails /and/\ncorrupts the test filesystem, every subsequent passing test will be\nmarked as a failure because of latent corruptions on the test\nfilesystem.\n\nThis is a little silly, so let\u0027s call _check_filesystems on the test\nfilesystem after a test fail so that the badness doesn\u0027t spread.\n\nCc: fstests@vger.kernel.org # v2023.05.01\nFixes: 4a444bc19a836f (\"check: _check_filesystems for errors even if test failed\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "cc0dcbf488495efea9575785ae8566280f232e58", "tree": "de26404b4183434aace843a414d92b313d220e8b", "parents": [ "34d0c55a92b5b637f49b4b90591c8db29cf396cd" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:42:38 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 21:43:29 2025 +0800" }, "message": "check: unbreak iam\n\nI don\u0027t know why this change was made:\n\niam\u003dcheck\n\nto\n\niam\u003dcheck.$$\n\nThe only users of this variable are:\n\ncheck:36:iam\u003dcheck\ncheck:52:rm -f $tmp.list $tmp.tmp $tmp.grep $here/$iam.out $tmp.report.* $tmp.arglist\ncommon/btrfs:216: if [ \"$iam\" !\u003d \"check\" ]; then\ncommon/overlay:407: if [ \"$iam\" !\u003d \"check\" ]; then\ncommon/rc:3565: if [ \"$iam\" !\u003d \"check\" ]; then\ncommon/xfs:1021: if [ \"$iam\" !\u003d \"check\" ]; then\nnew:9:iam\u003dnew\n\nNone of them were ported to notice the pid. Consequently,\n_check_generic_filesystem (aka _check_test_fs on an ext4 filesystem)\nfailing will cause ./check to exit the entire test suite when the test\nfilesystem is corrupt. That\u0027s not what we wanted, particularly since\nLeah added a patch to repair the test filesystem between tests.\n\nCc: fstests@vger.kernel.org # v2024.12.08\nFixes: fa0e9712283f0b (\"fstests: check-parallel\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "34d0c55a92b5b637f49b4b90591c8db29cf396cd", "tree": "ee07baf68d61836403eb0b9e16dc51f244a92290", "parents": [ "c0de6df761000445ddd6134cec29015fef39310d" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:42:23 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 21:43:29 2025 +0800" }, "message": "generic/251: skip this test if fstrim geometry detection fails\n\nThere\u0027s no reason to wait until fstrim_loop to detect the length\nconstraints on the FITRIM call since failing to detect any constraints\njust leads to _notrun. Run that stuff from the top level scope so that\nwe don\u0027t start up a bunch of exercisers for no good reason.\n\nCc: fstests@vger.kernel.org # v2023.10.29\nFixes: 95b0db739400c2 (\"generic/251: check min and max length and minlen for FSTRIM\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "c0de6df761000445ddd6134cec29015fef39310d", "tree": "857715f8b8c90978415a101b9ee23db05159d7e1", "parents": [ "aac2e9fee68b6e998de86655046f7c26613a6532" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed May 21 15:42:07 2025 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 23 21:43:29 2025 +0800" }, "message": "generic/251: fix infinite looping if fstrim_loop configuration fails\n\nIn generic/251, the topmost scope of the test creates a run file\n($tmp.fstrim_loop), starts fstrim_loop as a background shell, and then\nwaits for the file to disappear. Unfortunately, the set_*_constraints\nhelpers called by fstrim_loop can abort the subshell by invoking\n_notrun, in which case the loop never deletes the runfile and the upper\nscope waits forever.\n\nFix this by amending _destroy_fstrim to delete the runfile always, and\nmove the trap call to the top of the function with a note about why it\nmust always be called.\n\nOh but wait, there\u0027s a second runfile related bug in run_process -- if\nthe fstrim loop exits while run_process is looping, it\u0027ll keep looping\neven though there isn\u0027t anything else going on. Break out of the loopin\nthis case.\n\nOh but wait, there\u0027s a /third/ runfile bug -- if the fstrim_loop exits\nbefore the run_process children, it will delete the runfile. Then the\ntop level scope, in trying to empty out the runfile to get the\nfstrim_loop to exit, recreates the runfile and waits forever for nobody\nto delete the run file.\n\nI hate process management in bash.\n\nCc: fstests@vger.kernel.org # v2024.12.01\nFixes: 2d6e7681acff1e (\"generic/251: use sentinel files to kill the fstrim loop\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "aac2e9fee68b6e998de86655046f7c26613a6532", "tree": "d27664811a8a6e81f893dd2c88325c7a4a40655f", "parents": [ "f405f5f6cc8e5c33e11f8bb0b0256d1753720d2f" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Wed May 14 18:13:32 2025 +0100" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed May 21 13:38:45 2025 +0800" }, "message": "fstests: add a mmap test group\n\nAdd a mmap group to tag tests that exercise memory mapped reads/writes, so\nthat it\u0027s easy to filter and run tests that exercise map:\n\n ./check -g mmap\n\nVery useful during development to quickly test changes to a filesystem\u0027s\nmmap implementation.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "f405f5f6cc8e5c33e11f8bb0b0256d1753720d2f", "tree": "2ef14d0051c6f16c50c40e3cb094b14cdff9ec35", "parents": [ "0e88b42adfbc15dcfb84312f1d7acb2b245be161" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Mon May 19 14:58:39 2025 +0930" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed May 21 12:57:40 2025 +0800" }, "message": "fstests: generic/537: remove the btrfs specific mount option\n\nAlthough btrfs deprecated \"norecovery\" mount option in upstream kernel\ncommit a1912f712188 (\"btrfs: remove code for inode_cache and recovery\nmount options\"), later \"norecovery\" mount option is re-introduced for\ncompatibility by commit 440861b1a03c (\"btrfs: re-introduce \u0027norecovery\u0027\nmount option\").\n\nInstead the btrfs specific mount option \"nologreplay\" is already\ndeprecated for a long time and is going to be removed soon.\n\nSo use the generic \"norecovery\" for all filesystems.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "0e88b42adfbc15dcfb84312f1d7acb2b245be161", "tree": "83c6e744c4b963b24a206ea3ba8a096bee26a201", "parents": [ "f0477f43d20391e06934e1596646a20503a24563" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue May 13 07:19:33 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun May 18 21:57:16 2025 +0800" }, "message": "xfs: skip test that want to mdrestore to block devices on zoned devices\n\nmdrestore doesn\u0027t work on zoned device, so skip tests using to\npre-populate a file system image.\n\nThis was previously papered over by requiring fallocate, which got\nremoved in commit eff1baf42a79 (\"common/populate: drop fallocate mode 0\nrequirement\").\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "f0477f43d20391e06934e1596646a20503a24563", "tree": "a3db14b80a5b89d2bb617d357b1cb2f2cf87ad44", "parents": [ "e161fc34861a36838d03b6aad5e5b178f2a4e8e1" ], "author": { "name": "Nirjhar Roy (IBM)", "email": "nirjhar.roy.lists@gmail.com", "time": "Fri Jan 10 09:10:25 2025 +0000" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Tue May 13 11:49:47 2025 +0800" }, "message": "tests/selftest: Add a new pseudo flaky test.\n\nThis test is to simulate the behavior of a flaky test. This will be required\nwhen we will make some modifications to the pass/fail metric calculation of\nthe test infrastructure where we will need a test with non-zero pass\nand non-zero failure rate.\n\nReviewed-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nSigned-off-by: Nirjhar Roy (IBM) \u003cnirjhar.roy.lists@gmail.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e161fc34861a36838d03b6aad5e5b178f2a4e8e1", "tree": "9220efb2f3e1206adaa0a7b0a0314ac4d2659a40", "parents": [ "1d47ece860617e436947ff546145b7291e95346f" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Wed May 07 13:36:42 2025 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun May 11 22:30:30 2025 +0800" }, "message": "f2fs/012: test red heart lookup\n\nAs Han Qi reported in bugzilla [1], commit 5c26d2f1d3f5 (\"unicode: Don\u0027t\nspecial case ignorable code points\") changes logic to handle ignorable\ncode points, when we handle filename which has special unicode charactor\nlike red heart ❤️, utf8_casefold() may return different length than in the\npast, result in that f2fs cacluates hash code incorreclty, eventually,\nfilename w/ special unicode charactor will not be found w/ the wrong hash\ncode.\n\nf2fs has introduced a linear lookup fallback w/ commit 91b587ba79e1\n(\"f2fs: Introduce linear search for dentries\"), once hash-based lookup\nfails, it tries linear lookup as a fallback.\n\nThis patch can help to check whether linear lookup fallback works well\nor not.\n\nFirstly, we use below testcase to check how hash code changes:\n\nmkfs.f2fs -f -O casefold -C utf8 /dev/vda\nmount /dev/vda /mnt/f2fs\nmkdir /mnt/f2fs/dir/\nf2fs_io setflags casefold /mnt/f2fs/dir\ntouch /mnt/f2fs/dir/$\u0027\\u2764\\ufe0f\u0027\numount /mnt/f2fs\ndump.f2fs -i 4 -d 3 /dev/vda\ndump.f2fs -b $blkaddr_of_dir -d 3 /dev/vda\n\nw/o (\"unicode: Don\u0027t special case ignorable code points\")\n[dump_dirent: 991] bitmap pos[0x2] name[❤️] len[0x6] hash[0x19dd7132] ino[0x5] type[0x1]\n[dump_dirent: 998] name(hex)[0xe2 0x9d 0xa4 0xef 0xb8 0x8f 0x0]\n\nw/ (\"unicode: Don\u0027t special case ignorable code points\")\n[dump_dirent: 991] bitmap pos[0x2] name[❤️] len[0x6] hash[0x9a2ea068] ino[0x5] type[0x1]\n[dump_dirent: 998] name(hex)[0xe2 0x9d 0xa4 0xef 0xb8 0x8f 0x0]\n\nCorrect hash code:\t0x19dd7132\nWrong hash code:\t0x9a2ea068\n\nSo, we can test as below:\n\n1. create file w/ red heart as its filename\n2. inject wrong hash code to the file\n3. disable linear lookup, expect lookup failure\n4. enable linear lookup, expect lookup succeed\n\n[1] https://bugzilla.kernel.org/show_bug.cgi?id\u003d219586\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Daniel Lee \u003cchullee@google.com\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "1d47ece860617e436947ff546145b7291e95346f", "tree": "77e99fc86ec4b0b6682191a656563e027657dd5c", "parents": [ "cd5640a933811c6151e399991344ee750d797e4f" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Wed May 07 13:18:12 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun May 11 22:30:30 2025 +0800" }, "message": "generic/211: completely remove obsolete test and related code\n\nThis was a regression test for a bug in fs/aio.c kernel code that could\ncause kernel crashing and was fixed in commit 3e45a10919b3 (\"aio: remove\nincorrect initialization of \"nr_pages\"\") more than 20 years ago (in\nv2.6.10).\n\nThe test code was basically trying to trigger the bug by doing repeated\nmmaps until it would exhaust the vm.max_map_count limit, after which the\naio_setup_ring() would fail its own internal mmap and branch into\naio_free_ring() where it would attempt to free pages that were not\nallocated and crash the kernel.\n\nThe bug is was not really relevant to filesystems in the first place,\nand further to its fix it was made not possible to trigger due to commit\n3dc9acb67600 (\"aio: clean up and fix aio_setup_ring page mapping\").\n\nThe test currently triggers the oom killer on systems where the\nvm.max_map_count limit has been increased significantly from the default\nas it eventually exhausts the available memory. This could be trivially\nfixed by lowering and then restoring the limit just for the duration of\nthe test, but since it no longer serves any purpose let\u0027s drop it\ncompletely.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "cd5640a933811c6151e399991344ee750d797e4f", "tree": "b50ca14c636cb3f17611a016cb12f62ede21efb6", "parents": [ "414de1b79cd72368d216d6f9443fbf5e10f5931c" ], "author": { "name": "Hans Holmberg", "email": "Hans.Holmberg@wdc.com", "time": "Thu May 08 07:34:45 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 09 03:18:13 2025 +0800" }, "message": "xfs: test that we can handle spurious zone wp advancements\n\nTest that we can gracefully handle spurious zone write pointer\nadvancements while unmounted.\n\nAny space covered by the wp unexpectedly moving forward should just\nbe treated as unused space, so check that we can still mount the file\nsystem and that the zone will be reset when all used blocks have been\nfreed.\n\nSigned-off-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "414de1b79cd72368d216d6f9443fbf5e10f5931c", "tree": "e37d9f80fe102b147973be62f55934080efd0e51", "parents": [ "d6c292e41ccec1ad1b8335a3f339ab6ea2b2d574" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu May 08 07:34:44 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 09 03:17:17 2025 +0800" }, "message": "xfs: test that truncate does not spuriously return ENOSPC\n\nFor zoned file systems, truncate to an offset not aligned to the block\nsize need to allocate a new block for zeroing the remainder.\n\nTest that this allocation can dip into the reserved pool even when other\nthreads are waiting for space freed by GC.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d6c292e41ccec1ad1b8335a3f339ab6ea2b2d574", "tree": "fdfb2cb98ddcd895b70772ec6c3bfa9111269673", "parents": [ "c63fc5f066c11151baf8a64b3bcfafa313e31701" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu May 08 07:34:43 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 09 03:17:17 2025 +0800" }, "message": "xfs: test that xfs_repair does not mess up the zone used counter\n\nCheck that xfs_repair actually rebuilds the used counter after blowing\naway the rmap inode and recreating it.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "c63fc5f066c11151baf8a64b3bcfafa313e31701", "tree": "8e24388245277389877d235ed41ac7e249fc68ba", "parents": [ "57e6890bbce2fc12d75c0d404b4c8f4ee2069f30" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu May 08 07:34:42 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 09 03:17:17 2025 +0800" }, "message": "xfs: test zoned GC file defragmentation for random writers\n\nTest that zoned GC defragments sequential writers forced into the same\nzone.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "57e6890bbce2fc12d75c0d404b4c8f4ee2069f30", "tree": "16cceeba0cb14c5fb9f6270c508b8d85335953f5", "parents": [ "0a014baacc4c2a56728a94c6da272febccc1cceb" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu May 08 07:34:41 2025 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri May 09 03:17:17 2025 +0800" }, "message": "xfs: test zoned GC file defragmentation for sequential writers\n\nTest that zoned GC defragments sequential writers forced into the same\nzone.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" } ], "next": "0a014baacc4c2a56728a94c6da272febccc1cceb" }