From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"dm-devel@lists.linux.dev" <dm-devel@lists.linux.dev>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
hch <hch@lst.de>, "tytso@mit.edu" <tytso@mit.edu>,
"djwong@kernel.org" <djwong@kernel.org>,
"bmarzins@redhat.com" <bmarzins@redhat.com>,
"chaitanyak@nvidia.com" <chaitanyak@nvidia.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"yi.zhang@huawei.com" <yi.zhang@huawei.com>,
"chengzhihao1@huawei.com" <chengzhihao1@huawei.com>,
"yukuai3@huawei.com" <yukuai3@huawei.com>,
"yangerkun@huawei.com" <yangerkun@huawei.com>
Subject: Re: [PATCH blktests v2 0/3] blktest: add unmap write zeroes tests
Date: Sun, 17 Aug 2025 06:14:14 +0000 [thread overview]
Message-ID: <7dswufawxmyqblokjesulhdexqld3bx7sycgmylbaeqs43ougk@25rseyqm3beg> (raw)
In-Reply-To: <20250813024421.2507446-1-yi.zhang@huaweicloud.com>
On Aug 13, 2025 / 10:44, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
>
> Change since v2:
> - Modify the sysfs interfaces according to the kernel implementation.
> - Determine whether the kernel supports it by directly checking the
> existence of the sysfs interface, instead of using device_requries().
> - Drop _short_dev() helper and directly use _real_dev() to acquire dm
> path.
> - Check the return value of setup_test_device().
> - Fix the '"make check'" errors.
>
>
> The Linux kernel (since version 6.17)[1] supports FALLOC_FL_WRITE_ZEROES
> in fallocate(2) and add max_{hw|user}_wzeroes_unmap_sectors parameters
> to the block device queue limit. These tests test those block device
> unmap write zeroes sysfs interface
>
> /sys/block/<disk>/queue/write_zeroes_max_bytes
> /sys/block/<disk>/queue/write_zeroes_unmap_max_hw_bytes
>
> with various SCSI/NVMe/device-mapper devices.
>
> The value of /sys/block//queue/write_zeroes_unmap_max_hw_bytes should be
> equal to a nonzero value of /sys/block//queue/write_zeroes_max_bytes if
> the block device supports the unmap write zeroes command; otherwise, it
> should return 0. We can also disable unmap write zeroes command by
> setting /sys/block/<disk>/queue/write_zeroes_max_bytes to 0.
>
> - scsi/010 test SCSI devices.
> - dm/003 test device mapper stacked devices.
> - nvme/065 test NVMe devices.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=278c7d9b5e0c
I applied this v2 series. Of note is that I amended the 2nd and 3rd patches to
fix the shellcheck warnings below. Anyway, thanks for the patches!
$ make check
shellcheck -x -e SC2119 -f gcc check common/* \
tests/*/rc tests/*/[0-9]*[0-9] src/*.sh
common/rc:679:7: note: Double quote to prevent globbing and word splitting. [SC2086]
tests/nvme/065:44:7: warning: Quote this to prevent word splitting. [SC2046]
tests/nvme/065:44:7: note: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'. [SC2005]
make: *** [Makefile:21: check] Error 1
next prev parent reply other threads:[~2025-08-17 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 2:44 [PATCH blktests v2 0/3] blktest: add unmap write zeroes tests Zhang Yi
2025-08-13 2:44 ` [PATCH blktests v2 1/3] scsi/010: " Zhang Yi
2025-08-13 2:44 ` [PATCH blktests v2 2/3] dm/003: " Zhang Yi
2025-08-13 2:44 ` [PATCH blktests v2 3/3] nvme/065: " Zhang Yi
2025-08-17 6:14 ` Shinichiro Kawasaki [this message]
2025-08-18 1:42 ` [PATCH blktests v2 0/3] blktest: " Zhang Yi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7dswufawxmyqblokjesulhdexqld3bx7sycgmylbaeqs43ougk@25rseyqm3beg \
--to=shinichiro.kawasaki@wdc.com \
--cc=bmarzins@redhat.com \
--cc=brauner@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=chengzhihao1@huawei.com \
--cc=djwong@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).