{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":89751386,"defaultBranch":"master","name":"blktests","ownerLogin":"osandov","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2017-04-28T23:17:34.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3682206?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1609799707.0","currentOid":""},"activityList":{"items":[{"before":"ed9b60a05a3f575303cce6f104fc9d28b417c36b","after":"80430afc55893e12bbd2faf04e288856446b34d9","ref":"refs/heads/master","pushedAt":"2024-09-06T07:40:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/052: wait for namespace removal before recreating namespace\n\nThe CKI project reported that the test case nvme/052 fails occasionally\nwith the errors below:\n\n nvme/052 (tr=loop) (Test file-ns creation/deletion under one subsystem) [failed]\n runtime ... 22.209s\n --- tests/nvme/052.out 2024-07-30 18:38:29.041716566 -0400\n +++\n+/mnt/tests/gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/archive/production/kernel-t\\\nests-production.zip/storage/blktests/nvme/nvme-loop/blktests\n+/results/nodev_tr_loop/nvme/052.out.bad 2024-07-30 18:45:35.438067452 -0400\n @@ -1,2 +1,4 @@\n Running nvme/052\n +cat: /sys/block/nvme1n2/uuid: No such file or directory\n +cat: /sys/block/nvme1n2/uuid: No such file or directory\n Test complete\n\nThe test case repeats creating and removing namespaces. When the test\ncase removes the namespace by echoing 0 to the sysfs enable file, this\necho write does not wait for the completion of the namespace removal.\nBefore the removal completes, the test case recreates the namespace.\nAt this point, the sysfs uuid file for the old namespace still exists.\nThe test case misunderstands that the the sysfs uuid file would be for\nthe recreated namespace, and tries to read it. However, the removal\nprocess for the old namespace deletes the sysfs uuid file at this point.\nThen the read attempt fails and results in the errors.\n\nTo avoid the failure, wait for the namespace removal before recreating\nthe namespace. Modify nvmf_wait_for_ns() so that it can wait for\nnamespace creation and removal. Call nvmf_wait_for_ns() for removal\nafter _remove_nvmet_ns() call. While at it, reduce the wait time unit\nfrom 1 second to 0.1 second to shorten test time.\n\nThe test case intends to catch the regression fixed by the kernel commit\nff0ffe5b7c3c (\"nvme: fix namespace removal list\"). I reverted the commit\nfrom the kernel v6.11-rc4, then confirmed that the test case still can\ncatch the regression with this change.\n\nLink: https://lore.kernel.org/linux-block/tczctp5tkr34o3k3f4dlyhuutgp2ycex6gdbjuqx4trn6ewm2i@qbkza3yr5wdd/\nFixes: 077211a0e9ff (\"nvme: add test for creating/deleting file-ns\")\nSigned-off-by: Shin'ichiro Kawasaki \nReviewed-by: Nilay Shroff ","shortMessageHtmlLink":"nvme/052: wait for namespace removal before recreating namespace"}},{"before":"fcd680f2166ab3c4be788da2676a6ff2c599b745","after":"ed9b60a05a3f575303cce6f104fc9d28b417c36b","ref":"refs/heads/master","pushedAt":"2024-09-06T03:01:43.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme: add test for controller rescan under I/O load\n\nAdd a test that repeatedly rescans nvme controllers while doing IO\non an nvme namespace connected to these controllers. The purpose\nof the test is to make sure that no I/O errors or data corruption\noccurs because of the rescan operations. The test uses sub-second\nsleeps, which can't be easily accomplished in bash because of\nmissing floating-point arithmetic (and because usleep(1) isn't\nportable). Therefore an awk program is used to trigger the\ndevice rescans.\n\nLink: https://lore.kernel.org/linux-nvme/20240822201413.112268-1-mwilck@suse.com/\nSigned-off-by: Martin Wilck \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme: add test for controller rescan under I/O load"}},{"before":"25efe2a1948d6ebdb073cbe8a7da3a012b4c329c","after":"fcd680f2166ab3c4be788da2676a6ff2c599b745","ref":"refs/heads/master","pushedAt":"2024-08-09T02:08:09.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"zbd/011: add test for DM resource limits stacking\n\nSince the kernel commit 73a74af0c72b (\"dm: Improve zone resource limits\nhandling\"), zone resource limits (max open zones and max active zones)\nare propagated from target zoned devices to mapped devices. As the\nkernel commit message describes, the resource limit propagation shall\nfollow the two rules below based on the number of sequential zones\nmapped by the targets:\n\n1) For a target mapping an entire zoned block device, the limits for the\n target are set to the limits of the device.\n2) For a target partially mapping a zoned block device, the number of\n mapped sequential zones is used to determine the limits: if the\n target maps more sequential write required zones than the device\n limits, then the limits of the device are used as-is. If the number\n of mapped sequential zones is lower than the limits, then we assume\n that the target has no limits (limits set to 0).\n\nAdd a new test case to confirm that the resource limit propagation\nfollows the rules. Prepare two zoned null_blk devices with different\nset ups: number of conventional zones, different max open zones and max\nactive zones limits. Create variations of DMs using the null_blk devices\nand check if the max open zones and the max active zones have expected\nvalues.\n\nSuggested-by: Damien Le Moal \nSigned-off-by: Damien Le Moal \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"zbd/011: add test for DM resource limits stacking"}},{"before":"a24a7b462816fbad7dc6c175e53fcc764ad0a822","after":"25efe2a1948d6ebdb073cbe8a7da3a012b4c329c","ref":"refs/heads/master","pushedAt":"2024-07-30T01:48:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"dm/002: add --retry option to dmsetup remove command\n\nThe test case dm/002 rarely fails with the message below:\n\ndm/002 => nvme0n1 (dm-dust general functionality test) [failed]\n runtime 0.204s ... 0.174s\n --- tests/dm/002.out 2024-06-14 14:37:40.480794693 +0900\n +++ /home/shin/Blktests/blktests/results/nvme0n1/dm/002.out.bad 2024-06-14 21:38:18.588976499 +0900\n @@ -7,4 +7,6 @@\n countbadblocks: 0 badblock(s) found\n countbadblocks: 3 badblock(s) found\n countbadblocks: 0 badblock(s) found\n +device-mapper: remove ioctl on dust1 failed: Device or resource busy\n +Command failed.\n Test complete\nmodprobe: FATAL: Module dm_dust is in use.\n\nWhen udev opens the dm device, \"dmsetup remove\" command also tries to\nopen the device and fails with EBUSY. To avoid the failure, add the\n--retry option to the dmsetup command.\n\nSuggested-by: Milan Broz \nReviewed-by: Christoph Hellwig \nTested-by: Nitesh Shetty \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"dm/002: add --retry option to dmsetup remove command"}},{"before":"0c3dfdda8c585c28903acdb3bcfa66b4fa04443d","after":"a24a7b462816fbad7dc6c175e53fcc764ad0a822","ref":"refs/heads/master","pushedAt":"2024-07-29T12:12:33.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"md: add regression test for \"md/md-bitmap: fix writing non bitmap pages\"\n\nA bug in md-bitmap has been discovered by setting up a md raid on top of\nnvme-tcp devices that has optimal io size larger than the allocated\nbitmap.\n\nThe following test reproduces the bug by setting up a md-raid on top of\nnvme-tcp device over ram device that sets the optimal io size by using\ndm-stripe.\n\nSigned-off-by: Ofir Gal \n[Shin'ichiro: improved test description comments]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"md: add regression test for \"md/md-bitmap: fix writing non bitmap pages\""}},{"before":"f79783b44a5bbab51826e2f1d1cad5bbbb5719e2","after":"0c3dfdda8c585c28903acdb3bcfa66b4fa04443d","ref":"refs/heads/master","pushedAt":"2024-07-26T07:42:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nbd/rc: check nbd-server port readiness in _start_nbd_server()\n\nRecently, CKI project reported nbd/001 and nbd/002 failure with the\nerror message \"Socket failed: Connection refused\". It is suspected nbd-\nserver is not yet ready when nbd-client connects for the first time.\n\nTo avoid the failure, wait for the nbd-server start listening to the\nport at the end of _start_nbd_server(). For that purpose, use\n\"nbd-client -l\" command, which connects to the server and asks to list\navailable exports.\n\nReported-by: Yi Zhang \nLink: https://github.com/osandov/blktests/issues/142\nReviewed-by: Bart Van Assche \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nbd/rc: check nbd-server port readiness in _start_nbd_server()"}},{"before":"775a05859b0084e1c1b030dcd64b35a10c50fd0e","after":"f79783b44a5bbab51826e2f1d1cad5bbbb5719e2","ref":"refs/heads/master","pushedAt":"2024-07-17T02:03:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"loop/010: skip when kernel is older than v6.11\n\nPatch fixing test case issue which use to failed in old kernel, this\npatch skip test case if test runs in older kernel less than 6.11\n\nlog:\n\n[root@linux blktests]# ./check loop/010\nloop/010 (check stale loop partition) [not run]\n Kernel version too old\n\nSigned-off-by: Praveen K Pandey \n[Shin'ichiro: fixed trailing space, indent tab and commit message]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"loop/010: skip when kernel is older than v6.11"}},{"before":"077211a0e9ff03f6b07c695bcfbfc3bcaef449ea","after":"775a05859b0084e1c1b030dcd64b35a10c50fd0e","ref":"refs/heads/master","pushedAt":"2024-06-28T10:03:17.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"loop/010: do not assume /dev/loop0\n\nThe current implementation of the test case loop/010 assumes that the\nprepared loop device is /dev/loop0, which is not always true. When other\nloop devices are set up before the test case run, the assumption is\nwrong and the test case fails.\n\nTo avoid the failure, use the prepared loop device name stored in\n$loop_device instead of /dev/loop0. Adjust the grep string to meet the\ndevice name. Also use \"losetup --detach\" instead of\n\"losetup --detach-all\" to not detach the loop devices which existed\nbefore the test case runs.\n\nFixes: 1c4ae4fed9b4 (\"loop: Detect a race condition between loop detach and open\")\nReviewed-by: Gulam Mohamed \nReviewed-by: Chaitanya Kulkarni \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"loop/010: do not assume /dev/loop0"}},{"before":"f043065c3802987bcc3a46ca628f8cd0d27d8df4","after":"077211a0e9ff03f6b07c695bcfbfc3bcaef449ea","ref":"refs/heads/master","pushedAt":"2024-06-24T07:35:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme: add test for creating/deleting file-ns\n\nThis is regression test for commit be647e2c76b2 (nvme: use srcu for\niterating namespace list)[1]. It is fixed in commit ff0ffe5b7c3c(nvme:\nfix namespace removal list)[2].\n\nThis test uses a regular file backed loop device for creating and then\ndeleting an NVMe namespace in a loop.\n\n[1] https://lore.kernel.org/all/2312e6c3-a069-4388-a863-df7e261b9d70@linux.vnet.ibm.com/\n[2] https://lore.kernel.org/all/20240613164246.75205-1-kbusch@meta.com/\n\nSigned-off-by: Nilay Shroff \nReviewed-by: Daniel Wagner \nTested-by: Venkat Rao Bagalkote \nReviewed-by: Chaitanya Kulkarni \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme: add test for creating/deleting file-ns"}},{"before":"2271bef000fcae579d5ed4487d51762de5cd1c8d","after":"f043065c3802987bcc3a46ca628f8cd0d27d8df4","ref":"refs/heads/master","pushedAt":"2024-06-20T07:26:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"loop: Add regression test for unsupported backing file fallocate\n\nAdd the test case to confirm fix by the kernel commit 5f75e081ab5c (\"\nloop: Disable fallocate() zero and discard if not supported\").\n\nSigned-off-by: Cyril Hrubis \nReviewed-by: Chaitanya Kulkarni \n[Shin'ichiro: improved descriptions, used $loop_dev and long options]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"loop: Add regression test for unsupported backing file fallocate"}},{"before":"cae266bac8587cc4f49efe4ab61d5f15d53f1688","after":"2271bef000fcae579d5ed4487d51762de5cd1c8d","ref":"refs/heads/master","pushedAt":"2024-06-20T07:21:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"loop: Add regression test for unsupported backing file fallocate\n\nAdd the test case to confirm fix by the kernel commit 5f75e081ab5c (\"\nloop: Disable fallocate() zero and discard if not supported\").\n\nSigned-off-by: Cyril Hrubis \nReviewed-by: Chaitanya Kulkarni \n[Shin'ichiro: improved descriptions, used $loop_dev and long options]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"loop: Add regression test for unsupported backing file fallocate"}},{"before":"1c4ae4fed9b4dc28cededa31e713cc9d3690f9bd","after":"cae266bac8587cc4f49efe4ab61d5f15d53f1688","ref":"refs/heads/master","pushedAt":"2024-06-18T05:10:16.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nbd/004: drop the check for \"couldn't allocate config\" message\n\nThe test case nbd/004 was created to confirm the fix by the kernel\ncommit 06c4da89c24e (\"nbd: call genl_unregister_family() first in\nnbd_cleanup()\"). Originally, the test case was created to check that the\nkernel commit avoided a BUG. But the BUG was not recreated on my system\neven without the kernel commit, so I was not able to confirm that the\ntest case was working as expected. On the other hand, I found that the\nkernel commit avoided the two other kernel messages \"couldn't allocate\nconfig\" and \"cannot create duplicate filename\" on my test system. Then I\nsuggested adding the checks for those messages to the test case, and the\nchecks were added [1].\n\nHowever, it turned out that the kernel commit did not totally avoid the\nmessage \"couldn't allocate config\". The test case still makes the kernel\nreport the message with a low ratio. The failure is recreated when the\ntest case is repeated around 30 times. The CKI project reported that\nnbd/004 fails due to the message [2].\n\nWhen the failure happens, try_module_get() fails in nbd_genl_context():\n\nnbd_genl_connect()\n nbd_alloc_and_init_config()\n try_module_get() ... fails\n\nThis try_module_get() call checks that the module is not unloaded during\nthe connect operation. The test case does \"module load/unload\nconcurrently with connect/disconnect\" then the try_module_get() failure\nis expected. It means the failure is false-positive.\n\nDrop the wrong check for \"couldn't allocate config\" message. Still keep\nthe check for \"cannot create duplicate filename\".\n\n[1] https://lore.kernel.org/linux-block/20220707124945.c2rd677hjwkd7mim@shindev/\n[2] https://github.com/osandov/blktests/issues/140\n\nFixes: 349eb683fd06 (\"nbd: add a module load and device connect test\")\nReported-by: Yi Zhang \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nbd/004: drop the check for \"couldn't allocate config\" message"}},{"before":"6a36dea0bfacc74f91cdbf88bf2d3ceb5d93eb19","after":"1c4ae4fed9b4dc28cededa31e713cc9d3690f9bd","ref":"refs/heads/master","pushedAt":"2024-06-10T07:29:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"loop: Detect a race condition between loop detach and open\n\nWhen one process opens a loop device partition and another process detaches\nit, there will be a race condition due to which stale loop partitions are\ncreated causing IO errors. This test will detect the race.\n\nSigned-off-by: Gulam Mohamed \nReviewed-by: Chaitanya Kulkarni \n[Shin'ichiro: moved $TMPDIR reference into test()]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"loop: Detect a race condition between loop detach and open"}},{"before":"698f1a024cb4d69b4b6cd5500b72efa758340d05","after":"6a36dea0bfacc74f91cdbf88bf2d3ceb5d93eb19","ref":"refs/heads/master","pushedAt":"2024-06-07T04:40:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"README: add dependent command descriptions\n\nEven though many test cases assume the availability of the systemd-udev\nservice and the udevadm command, this dependency is not described. Add\nit to the dependency list. Also add optional dependencies to other\ncommands: mkfs.f2fs, mkfs.btrfs, nvme, nbd-client and nbd-server.\n\nReviewed-by: Chaitanya Kulkarni \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"README: add dependent command descriptions"}},{"before":"e263a0c718c2a9d45300798cc9a83fc3ad9f7cca","after":"698f1a024cb4d69b4b6cd5500b72efa758340d05","ref":"refs/heads/master","pushedAt":"2024-05-27T07:33:08.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"blktests: fix how we handle waiting for nbd to connect\n\nBecause NBD has the old style configure the device directly config we\nsometimes have spurious failures where the device wasn't quite ready\nbefore the rest of the test continued.\n\nnbd/002 had been using _wait_for_nbd_connect, however this helper waits\nfor the recv task to show up, which actually happens slightly before the\nsize is set and we're actually ready to be read from. This means we\nwould sometimes fail nbd/002 because the device wasn't quite right.\n\nAdditionally nbd/001 has a similar issue where we weren't waiting for\nthe device to be ready before going ahead with the test, which would\ncause spurious failures.\n\nFix this by adjusting _wait_for_nbd_connect to only exit once the size\nfor the device is being reported properly, meaning that it's ready to be\nread from.\n\nThen add this call to nbd/001 to eliminate the random failures we would\nsee with this test.\n\nSigned-off-by: Josef Bacik \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"blktests: fix how we handle waiting for nbd to connect"}},{"before":"dd845a782268ae386ad848d8c0c57c19339a4531","after":"e263a0c718c2a9d45300798cc9a83fc3ad9f7cca","ref":"refs/heads/master","pushedAt":"2024-05-09T09:01:51.000Z","pushType":"push","commitsCount":17,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/rc,srp/rc,common/multipath-over-rdma: rename use_rxe to USE_RXE\n\nTo follow uppercase letter guide of environment variables, rename\nuse_rxe to USE_RXE.\n\nReviewed-by: Daniel Wagner \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme/rc,srp/rc,common/multipath-over-rdma: rename use_rxe to USE_RXE"}},{"before":"f6f2d82b32b06d725b72ebb6b2efb72d5805bcf9","after":"dd845a782268ae386ad848d8c0c57c19339a4531","ref":"refs/heads/master","pushedAt":"2024-05-09T07:32:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/039: adjust to util-linux v2.40 dmesg format change\n\nSince util-linux version 2.40, dmesg supports \"caller ID\". When Linux\nkernel supports CONFIG_PRINTK_CALLER, dmesg adds thread ID or CPU ID\nwith parenthesis such as [ T123] or [ C16] to each message. This\nmade the dmesg string check of the test case nvme/039 fail. Fix this by\nfiltering out the added caller ID field.\n\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme/039: adjust to util-linux v2.40 dmesg format change"}},{"before":"d54b96ea1d962b5b279e0c66f256d72611f6d25c","after":"f6f2d82b32b06d725b72ebb6b2efb72d5805bcf9","ref":"refs/heads/master","pushedAt":"2024-04-25T11:22:34.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nbd/002: repeat partition existence check for ioctl interface\n\nWhen nbd-client is set up with the ioctl interface, it takes some time\nfor the nbd driver and the block layer to complete the partition read.\nThe test script calls stat command for the /dev/nbd0p1 device to check\nthe partition exists as expected. However, this stat command is often\ncalled before the partition read completion, then causes the test case\nfailure.\n\nTo avoid the test case failure, repeat the partition check a few times\nwith one second wait.\n\nTested-by: Yi Zhang \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nbd/002: repeat partition existence check for ioctl interface"}},{"before":"2525de37aa0db54d5a44f93e63cb1ee1ce5a73ea","after":"d54b96ea1d962b5b279e0c66f256d72611f6d25c","ref":"refs/heads/master","pushedAt":"2024-04-23T09:20:20.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"Merge pull request #139 from yizhanglinux/dev-240419-misc-fix\n\nblktests misc fix","shortMessageHtmlLink":"Merge pull request #139 from yizhanglinux/dev-240419-misc-fix"}},{"before":"89bdb5dd5326299d6b16680438e8cb3fe1ea4afc","after":"2525de37aa0db54d5a44f93e63cb1ee1ce5a73ea","ref":"refs/heads/master","pushedAt":"2024-04-23T06:38:27.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"block/033: additional fix\n\nThe previous commit moved the UBLK_PROG definition from tests/ublk/rc to\ncommon/ublk end. Move that again from common/ublk end to start. Also,\nthe UBLK_PROG local variable in block/033 is no longer required. Remove\nit.\n\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"block/033: additional fix"}},{"before":"56d7e5396b3405b99b45326c27b9f217b208512a","after":"89bdb5dd5326299d6b16680438e8cb3fe1ea4afc","ref":"refs/heads/master","pushedAt":"2024-04-18T06:36:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"block/037: add test to cover blk-cgroup vs. disk rebind\n\nRecently it is observed that list corruption is triggered when running\nscsi disk rebind in case of blk-cgroup.\n\nAdd one such test case for covering this unusual operation.\n\nCc: Changhui Zhong \nSigned-off-by: Ming Lei \n[Shin'ichiro: changed the test case number from block/035 to block/037]\n[Shin'ichiro: removed the _have_fio call and improved test description]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"block/037: add test to cover blk-cgroup vs. disk rebind"}},{"before":"13e12b7fa85b3e6a892605320a2ce5cba0079d5c","after":"56d7e5396b3405b99b45326c27b9f217b208512a","ref":"refs/heads/master","pushedAt":"2024-04-12T07:03:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"block/036: test return EIO from BLKRRPART\n\nWhen we fail to reread the partition superblock from the disk, due to\nbad sector or bad disk etc, BLKRRPART should fail with EIO.\nSimulate failure for the entire block device and run\n\"blockdev --rereadpt\" and expect it to fail and return EIO instead of\npass.\n\nLink: https://lore.kernel.org/all/20240405014253.748627-1-saranyamohan@google.com/\nSigned-off-by: Saranya Muruganandam \n[Shin'ichiro: changed the test case number from block/035 to block/036]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"block/036: test return EIO from BLKRRPART"}},{"before":"b97cfd822a3da3efaecd8dc14f557dc4cbc88824","after":"13e12b7fa85b3e6a892605320a2ce5cba0079d5c","ref":"refs/heads/master","pushedAt":"2024-04-10T07:05:29.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"Merge pull request #137 from bvanassche/master\n\nblock/035: Report IOPS","shortMessageHtmlLink":"Merge pull request #137 from bvanassche/master"}},{"before":"f073dacae5db8afc9bcef09884c2114f95090ef6","after":"b97cfd822a3da3efaecd8dc14f557dc4cbc88824","ref":"refs/heads/master","pushedAt":"2024-04-09T08:36:51.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"Merge pull request #136 from bvanassche/data-lifetime\n\nscsi/008: Add a data lifetime test","shortMessageHtmlLink":"Merge pull request #136 from bvanassche/data-lifetime"}},{"before":"0e40b259344891b9e7674dada608c800639b7994","after":"f073dacae5db8afc9bcef09884c2114f95090ef6","ref":"refs/heads/master","pushedAt":"2024-04-09T06:33:22.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"Merge pull request #135 from bvanassche/master\n\nblock/035: Test shared queue fairness","shortMessageHtmlLink":"Merge pull request #135 from bvanassche/master"}},{"before":"7ad75ddc51e9455e5b1941546a779f2ff1d87ce8","after":"0e40b259344891b9e7674dada608c800639b7994","ref":"refs/heads/master","pushedAt":"2024-04-08T03:55:50.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/rc: fix shellcheck warning SC2086\n\ntests/nvme/rc:1056:7: note: Double quote to prevent globbing and word splitting. [SC2086]\ntests/nvme/rc:1057:7: note: Double quote to prevent globbing and word splitting. [SC2086]\n\nThe warnings are observed with ShellCheck version 0.8.0. They are not\nobserved with ShellCheck version 0.9.0 and 0.10.0.\n\nFixes: 369d310 (\"nvme: Add passthru error logging tests to nvme/039\")\nSigned-off-by: Yi Zhang \n[Shin'ichiro: noted ShellCheck version dependency]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme/rc: fix shellcheck warning SC2086"}},{"before":"607513e64e48c098bb10740453318e40493e27b7","after":"7ad75ddc51e9455e5b1941546a779f2ff1d87ce8","ref":"refs/heads/master","pushedAt":"2024-03-29T07:57:40.000Z","pushType":"push","commitsCount":20,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/028: drop unused nvmedev\n\nNothing uses nvmedev, so just remove it.\n\nSigned-off-by: Daniel Wagner \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme/028: drop unused nvmedev"}},{"before":"0520ff2417188c2e24e0ac9e4e4b87d4acb06fd9","after":"607513e64e48c098bb10740453318e40493e27b7","ref":"refs/heads/master","pushedAt":"2024-03-05T01:18:53.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nvme/048: make queue count check retry-able\n\nWe are racing with the reset path of the controller. That means, when we\nset a new queue count, we might not observe the resetting state in time.\nThus, first check if we see the correct queue count and then the\ncontroller state.\n\nReviewed-by: Chaitanya Kulkarni \nSigned-off-by: Daniel Wagner \n[Shin'ichiro: removed unnecessary if block in nvmf_check_queue_count()]\nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nvme/048: make queue count check retry-able"}},{"before":"c6f99ad0e6f318cbdaa4643bca24088d3af9da14","after":"0520ff2417188c2e24e0ac9e4e4b87d4acb06fd9","ref":"refs/heads/master","pushedAt":"2024-03-01T11:46:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"nbd/001: wait for the device node to show up before running parted\n\nThe parted call can happen before the device is settled and thus fail.\nCurrently this happens very rarely for me (about 1 in 500 runs), but\na pending change to freeze the queues for updating the limits will make\nit much more likely to hit.\n\nSigned-off-by: Christoph Hellwig \nSigned-off-by: Shin'ichiro Kawasaki ","shortMessageHtmlLink":"nbd/001: wait for the device node to show up before running parted"}},{"before":"369d310fcd071e4b4488616e6b4bf71d324ae5cc","after":"c6f99ad0e6f318cbdaa4643bca24088d3af9da14","ref":"refs/heads/master","pushedAt":"2024-02-22T08:31:13.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"kawasaki","name":"Shin'ichiro Kawasaki","path":"/kawasaki","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/55551?s=80&v=4"},"commit":{"message":"Merge pull request #133 from yizhanglinux/dev-240219-nbd-001-fix\n\nnbd/001: change to use lsblk raw output format","shortMessageHtmlLink":"Merge pull request #133 from yizhanglinux/dev-240219-nbd-001-fix"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wNlQwNzo0MDoyMC4wMDAwMDBazwAAAASuphPE","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMi0yMlQwODozMToxMy4wMDAwMDBazwAAAAQBu4U1"}},"title":"Activity ยท osandov/blktests"}