From: Damien Le Moal <dlemoal@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>, Li Dong <lidong@vivo.com>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
"open list:DEVICE-MAPPER (LVM)" <dm-devel@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
opensource.kernel@vivo.com
Subject: Re: [PATCH] dm-table:fix zone block_device not aligned with zonesize
Date: Fri, 5 Jul 2024 10:08:32 +0900 [thread overview]
Message-ID: <afefbd10-e680-47c3-bd18-b3f2aae35a15@kernel.org> (raw)
In-Reply-To: <cd05398-cffa-f4ca-2ac3-74433be2316c@redhat.com>
On 7/5/24 00:29, Mikulas Patocka wrote:
>
>
> On Thu, 4 Jul 2024, Li Dong wrote:
>
>> For zone block devices, device_area_is_invalid may return an incorrect
>> value.
>>
>> Failure log:
>> [ 19.337657]: device-mapper: table: 254:56: len=836960256 not aligned to
>> h/w zone size 3244032 of sde
>> [ 19.337665]: device-mapper: core: Cannot calculate initial queue limits
>> [ 19.337667]: device-mapper: ioctl: unable to set up device queue for
>> new table.
>>
>> Actually, the device's zone length is aligned to the zonesize.
>>
>> Fixes: 5dea271b6d87 ("dm table: pass correct dev area size to device_area_is_valid")
>> Signed-off-by: Li Dong <lidong@vivo.com>
>> ---
>> drivers/md/dm-table.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
>> index 33b7a1844ed4..0bddae0bee3c 100644
>> --- a/drivers/md/dm-table.c
>> +++ b/drivers/md/dm-table.c
>> @@ -257,7 +257,7 @@ static int device_area_is_invalid(struct dm_target *ti, struct dm_dev *dev,
>> if (bdev_is_zoned(bdev)) {
>> unsigned int zone_sectors = bdev_zone_sectors(bdev);
>>
>> - if (start & (zone_sectors - 1)) {
>> + if (start % zone_sectors) {
>> DMERR("%s: start=%llu not aligned to h/w zone size %u of %pg",
>> dm_device_name(ti->table->md),
>> (unsigned long long)start,
>> @@ -274,7 +274,7 @@ static int device_area_is_invalid(struct dm_target *ti, struct dm_dev *dev,
>> * devices do not end up with a smaller zone in the middle of
>> * the sector range.
>> */
>> - if (len & (zone_sectors - 1)) {
>> + if (len % zone_sectors) {
>> DMERR("%s: len=%llu not aligned to h/w zone size %u of %pg",
>> dm_device_name(ti->table->md),
>> (unsigned long long)len,
>> --
>> 2.31.1.windows.1
>
> Hi
>
> This probably won't compile on 32-bit architectures because the operators
> for 64-bit divide and modulo don't work there.
>
> Please, rework the patch using dm_sector_div64.
This patch alone will not allow non power of 2 zone size drives to be supported
as the block layer will reject such drive in the first place. This patch should
be part of a larger series enabling such support. On its own, it is a NACK from
me for this change.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2024-07-05 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 15:15 [PATCH] dm-table:fix zone block_device not aligned with zonesize Li Dong
2024-07-04 15:29 ` Mikulas Patocka
2024-07-04 19:00 ` Non-power-of-2 zone size (was: [PATCH] dm-table:fix zone block_device not aligned with zonesize) Mikulas Patocka
2024-07-04 21:43 ` Pankaj Raghav (Samsung)
2024-07-05 0:13 ` Non-power-of-2 zone size Damien Le Moal
2024-07-05 1:08 ` Damien Le Moal [this message]
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=afefbd10-e680-47c3-bd18-b3f2aae35a15@kernel.org \
--to=dlemoal@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=lidong@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=opensource.kernel@vivo.com \
--cc=snitzer@kernel.org \
/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