Message ID | 20221006031829.37741-1-kch@nvidia.com (mailing list archive) |
---|---|
Headers | show |
Series | null_blk: allow REQ_OP_WRITE_ZEROES and cleanup | expand |
On 10/5/22 20:18, Chaitanya Kulkarni wrote: > Hi, > > In order to test the non-trivial I/O path in the block layer for > REQ_OP_WRITE_ZEROES allow write-zeroes on null_blk so we can write > testcases with and without non-memory backed mode followed by > few cleanup patches. > > Below is the test report with ext2/ext4 mkfs and a blktest > waiting to get upstream for this patch-series. > > -ck > I applied these patches on the latest linux-block/for-next [1], they apply seamlessly, is there anything missing in order to get it merged ? -ck [1] commit 6c944cdf52bb05a6572800a14edcea5a928a98a4 (origin/for-next) Merge: 939f803c54b0 5626196a5ae0 Author: Jens Axboe <axboe@kernel.dk> Date: Mon Nov 14 12:58:09 2022 -0700 Merge branch 'for-6.2/block' into for-next * for-6.2/block: md/raid1: stop mdx_raid1 thread when raid1 array run failed md/raid5: use bdev_write_cache instead of open coding it md: fix a crash in mempool_free md/raid0, raid10: Don't set discard sectors for request queue md/bitmap: Fix bitmap chunk size overflow issues md: introduce md_ro_state md: factor out __md_set_array_info() lib/raid6: drop RAID6_USE_EMPTY_ZERO_PAGE