From: John Garry <john.g.garry@oracle.com>
To: Zhang Yi <yi.zhang@huaweicloud.com>,
axboe@kernel.dk, linux-raid@vger.kernel.org
Cc: linux-block@vger.kernel.org, drbd-dev@lists.linbit.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
pmenzel@molgen.mpg.de, hch@lst.de, martin.petersen@oracle.com,
yi.zhang@huawei.com, yukuai3@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers
Date: Mon, 15 Sep 2025 11:43:05 +0100 [thread overview]
Message-ID: <370ca2e5-a4b2-4b5d-9fd1-a931dc2d1a6b@oracle.com> (raw)
In-Reply-To: <c7dd117e-6e3e-4b2d-a890-20f5c4bade2f@huaweicloud.com>
On 12/09/2025 07:16, Zhang Yi wrote:
> Hi, Jens!
>
> Can you take this patch set through the linux-block tree?
md raid maintainers,
please try to get this picked up ASAP. As things stand, all these RAID
personalities will be broken for 6.17 on drives supporting/reporting
write zeroes.
Thanks
>
> Thanks,
> Yi.
>
> On 9/10/2025 7:11 PM, Zhang Yi wrote:
>> From: Zhang Yi <yi.zhang@huawei.com>
>>
>> Changes since v1:
>> - Improve commit messages in patch 1 by adding a simple reproduction
>> case as Paul suggested and explaining the implementation differences
>> between RAID 0 and RAID 1/10/5, no code changes.
>>
>> v1: https://urldefense.com/v3/__https://lore.kernel.org/linux-block/20250825083320.797165-1-yi.zhang@huaweicloud.com/__;!!ACWV5N9M2RV99hQ!JAN4eq3ePrspeto0Hn7563lg3392Lh44jM1oTbgxbDoClxVOh5B73QhGD53f9tiLxuxfJCr51PyAP55COV2TTZAt$
>>
>> This series fixes the initialization of max_hw_wzeroes_unmap_sectors in
>> queue_limits for all md raid and drbd drivers, preventing
>> blk_validate_limits() failures on underlying devices that support the
>> unmap write zeroes command.
>>
>> Best regards,
>> Yi.
>>
>> Zhang Yi (2):
>> md: init queue_limits->max_hw_wzeroes_unmap_sectors parameter
>> drbd: init queue_limits->max_hw_wzeroes_unmap_sectors parameter
>>
>> drivers/block/drbd/drbd_nl.c | 1 +
>> drivers/md/md-linear.c | 1 +
>> drivers/md/raid0.c | 1 +
>> drivers/md/raid1.c | 1 +
>> drivers/md/raid10.c | 1 +
>> drivers/md/raid5.c | 1 +
>> 6 files changed, 6 insertions(+)
>>
>
>
next prev parent reply other threads:[~2025-09-15 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 11:11 [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers Zhang Yi
2025-09-10 11:11 ` [PATCH v2 1/2] md: init queue_limits->max_hw_wzeroes_unmap_sectors parameter Zhang Yi
2025-09-10 11:41 ` Hannes Reinecke
2025-09-17 1:20 ` Yu Kuai
2025-09-10 11:11 ` [PATCH v2 2/2] drbd: " Zhang Yi
2025-09-10 11:41 ` Hannes Reinecke
2025-09-12 6:16 ` [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers Zhang Yi
2025-09-15 10:43 ` John Garry [this message]
2025-09-16 0:49 ` Yu Kuai
2025-09-17 14:21 ` (subset) " Jens Axboe
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=370ca2e5-a4b2-4b5d-9fd1-a931dc2d1a6b@oracle.com \
--to=john.g.garry@oracle.com \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pmenzel@molgen.mpg.de \
--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).