{"shas":[["4342e767089ffda9924e0011695363b8d1f98c49","d55521028c14e0f378be5444e4ea388161c0d7e7@sandeen.net","xfstests 249: use -F option for xfs_io\n\nTest 249 was appearing to pass on ext4, but it wasn't really\nexercising the test due to lack of \"-F\" in the xfs_io arguments.\n\nWithout -F the files were created (oddly enough); neither pwrite\nnor sendfile were executed, and the diff of the two (empty)\nfiles passed, resulting in a passed test without testing anything.\n\nSo add the -F, capture the output, and test the result of each\nxfs_io invocation.\n\nAlso, when it fails, the diff output is huge.  Make diff silent,\nbut describe the diff failure and exit.\n\nSigned-off-by: Eric Sandeen <sandeen@redhat.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Eric Sandeen"],["188cf0a6d370f363c9aa8e8ba66e4f24f2a260aa","d55521028c14e0f378be5444e4ea388161c0d7e7@sandeen.net","xfstests: ensure selinux xattrs don't interfere with quota tests\n\n219 and 235 were failing on ext3 with selinux, because the extra\nxattrs upped the quota usage.\n\nDo the same trick we've used in the past to mount with an selinux\nglobal context when doing quota tests.\n\nNote the gross hack for remount,ro, though.\n\nSigned-off-by: Eric Sandeen <sandeen@redhat.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nReviewed-by: Alex Elder <aelder@sgi.com>","Eric Sandeen"],["9a4fb1b6756d9e8ba4f36e4c0f1e370ac1494a33","923f7720577207a44b32e59bbfbea59d27f1ae8e@lst.de","xfstests: allow deeper symlink recursion in 005\n\nRecent kernels allow more than 40 nested symlinks, so up the limit\nto still reproduce a failure.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Christoph Hellwig"],["3a4b6e0192805845b88adb63d25b0899fa0e2ad6","4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com","xfsqa: reduce error output on 229\n\nOnce we get one short write, we know the test has failed. We don't\nened to keep writing and getting more short writes and spewing\nthousands of errors to the console.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Eric Sandeen <sandeen@redhat.com>","Dave Chinner"],["b16ef33889f58a3d0b87eea2482ba7581c278422","78b342861d821967b29f951b7366f5a0267e0c38@redhat.com","xfstests 252: add test for fallocate with hole punching\n\nMove the major test meat of 242 into common.punch, and reuse it for\na new testcase the exercises the new fallocate implementation\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Christoph Hellwig <hch@lst.de>","Josef Bacik"],["3d3751a7b3121f4c0b78bac93feefb71d2858fe0","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: eliminate some warnings under dmapi/src\n\nEliminate build warnings reported on files located under these\nsubdirectories:\n    dmapi/src/common/cmd/\n    dmapi/src/common/lib/\n    dmapi/src/sample_hsm/\n    dmapi/src/simple/\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["eb84ef4de89a567c7f4ebade5acc0878a7fb90f7","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: eliminate warnings under dmapi/src/suite1/cmd (1)\n\nEliminate build warnings reported on files located under\ndmapi/src/suite1/cmd/ (first of three).\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["a2f9298d5ef14a38ed6c8aee6c16d3b5758197ce","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: eliminate warnings under dmapi/src/suite1/cmd (2)\n\nEliminate build warnings reported on files located under\ndmapi/src/suite1/cmd/ (second of three).\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["6fb34e2165b3fdea4269b45f39e83d7d1a2023f5","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: eliminate warnings under dmapi/src/suite1/cmd (3)\n\nEliminate build warnings reported on files located under\ndmapi/src/suite1/cmd/ (third of three).\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["d4ff3dd5306793e4a472cddedab83287c3e86039","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: eliminate warnings under dmapi/src/suite2/src\n\nEliminate build warnings reported on files located under\ndmapi/src/suite2/src/.\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["100f74846e8d372cc7b3f6f198a174fe3bb8d4e4","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: drop \"Mount point match\" from 028 and 047 golden output\n\nBill Kendall's latest update to xfsdump dropped a line of output\nthat served no real purpose.  This change updates the golden output\nfor the two tests that included that line of output.\n\nUpdated to filter out that line from dump output also, so old\nversions of the code will still produce the same output (suggested\nby Dave Chinner).\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>","Alex Elder"],["bf564e039941da7634af378fd437823709a5bc1b","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: make a few recently-added tests executable\n\nBy convention all of the tests in the xfstests suite have mode 0755.\nA few have recently committed without the execute bit set.\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["9935bd9855c34bccef5d180e9af110d3290c4e93","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: coalesce contiguous extents in extent map output\n\nThe specific set of extent sizes allocated to a file is not always\ndeterministic.  In particular, sometimes a range of unwritten blocks\nis covered by a single extent, while in other cases it might be\nrepresented by multiple consecutive unwritten extents.  This can\nresult in spurious errors being reported in tests that check file\nextent maps.\n\nAdd a filter that finds adjacent extents in what gets produced for\nfiemap and bmap output and coalesces them as if all consective\nextents of the same time were really just one extent.  (Note that\nas implemented here this applies to all extent types, not just\nunwritten extents.)\n\nUpdate the golden output for test 242 to reflect the change.\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["c8200ef31e0148224404858313eabf473b034205","f556392d917047d964350b9c68912016c96d5e94@sgi.com","xfstests: 253: test the metadump functionality of xfs_db\n\nThis patch creates a test that exercises xfs_metadump, with a focus\non its obfuscation of names.  It was created to verify fixes that\navoided a hang condition when running \"xfs_metadump\" on a directory\ncontaining files having particular bit patterns in their name.\nArkadiusz MiÅkiewicz first reported seeing this while attempting\nto create a metadump for a filesystem containing a file named\n\"R\\323\\257NE\".\n\nFor now this script checks the following (using only filenames, not\nattributes):\n- that short names (4 characters or less) aren't obfuscated\n- that long names get obfuscated\n- that (long) directory names get obfuscated\n- that names that are known to produce bit patterns that lead\n  to invalid path components still generate obfuscated names\n  (this could previously lead to a hang)\n- that many names of the same length can still generate new\n  obfuscated names (this could previously lead to a hang)\n- that neither \"lost+found\" nor orphaned files stored in it ge\n  obfuscated\n\nRight now there are two sets of \"ls\" commands executed (one before\nand one after obfuscation).  This produces repeatable results for\nme on one filesystem, but on a different filesystem I expect the\ninode numbers to change (and random number generation might change\nthe output too).  I'm interested in suggestions on how to filter\nthe output so the results can be verified.  If nothing else, the\ntest serves its purpose if I simply comment out those commands,\nand will do that if there's not a better suggstion.\n\nSigned-off-by: Alex Elder <aelder@sgi.com>\nReviewed-by: Dave Chinner <dchinner@redhat.com>","Alex Elder"],["30456902c622e2b50f4cfe98343f257d7a9df674","85dcca6eaef7f88f8513274f73363a9b5feab3ec@taobao.com","xfstests: fix error discard test output in 251.out\n\nI don't know why, but discard tests is 251 in xfs, but 251.out has\nnumber of 248 in it, So it fails.  Change it to 251 now.\n\nCc: Lukas Czerner <lczerner@redhat.com>\nCc: Christoph Hellwig <hch@lst.de>\nCc: Alex Elder <aelder@sgi.com>\nSigned-off-by: Tao Ma <boyu.mt@taobao.com>\nSigned-off-by: Alex Elder <aelder@sgi.com>","Tao Ma"],["7656052d6b073563531c17a59f23d3a2a1a91b7d","d55521028c14e0f378be5444e4ea388161c0d7e7@sandeen.net","xfstests: clean up fallocate configuration tests\n\nWhen I added fallocate support to fsx I inadvertently added\na duplicate fallocate test.\n\nConsolidate them both into one test (the link test, not the\ncompile test) and make all tests use \"true\" rather than \"yes\"\nto be more consistent with other tests.\n\nSigned-off-by: Eric Sandeen <sandeen@sandeen.net>\nReviewed-by: Alex Elder <aelder@sgi.com>","Eric Sandeen"],["0a818862bb74932e15971ec8bedb55765ec3a3f6","923f7720577207a44b32e59bbfbea59d27f1ae8e@lst.de","xfstests: support post-udev device mapper nodes\n\nBecause of udevs complaining device mapper now creates /dev/dm-N as the real\ndevice nodes, and just symlinks the /dev/mapper/ names to it.  This would be\neasy if everything used the /dev/mapper clear names, but most system utilities\ntranslate them back to the /dev/mapper/ names and thus confuse various test\ncases.  Add support to _is_block_dev to read symlinks, and add documentation\non how to run xfstests on device mapper volumes.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nReviewed-by: Alex Elder <aelder@sgi.com>","Christoph Hellwig"],["630421f6d44920601c39a008bdefa501593162b5","e6f2f3d5b819fd5bdcf5d18b7dcb052d2fa0a24f@redhat.com","xfstests: fsx: do not print fallocate support warning in quiet mode\n\nltp/fsx.c tests whether the filesystem it is run on supports fallocate.\nIf it is not supported the fsx will print warning to stderr. This leads\nto fails of tests 075, 112, 127 for the filesystems that do not support\nfallocate. The tests use ltp/fsx but do not filter out stderr. Since \nltp/fsx.c can work without fallocate support I propose to move this\nmessage to stdout unless quiet output is not requested. Previous patch\nprinted the message even if -q flag was used. This patch honours the flag.\n\nThis simple patch fixes the issue for me, tested on all the mentioned tests:\n\nSigned-off-by: Boris Ranto <branto@redhat.com>\nSigned-off-by: Eric Sandeen <sandeen@redhat.com>","Boris Ranto"],["8593459c6a770fee15e2aa1b06fd1659f1439c78","39b28f342388deb5b19584637eaeed658ed0d1e3@users.sf.net","fix scratch_mkfs for next4","Amir Goldstein"],["51956787f9d4794ee2c08f284e99c0ee5238ef23","39b28f342388deb5b19584637eaeed658ed0d1e3@users.sf.net","Merge remote-tracking branch 'upstream/master'\n\nConflicts:\n\tcommon.rc","Amir Goldstein"]],"ref":"refs/heads/master","size":21,"head":"5f0de2c1d40374ee3be4b0f40d32470f2bf9ab82","push_id":32226082}