From: Bart Van Assche <bvanassche@acm.org>
To: LongPing Wei <weilongping@oppo.com>, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, bvanassche@google.com, dlemoal@kernel.org
Subject: Re: [PATCH v4] block: get wp_offset by bdev_offset_from_zone_start
Date: Tue, 10 Dec 2024 12:23:31 -0800 [thread overview]
Message-ID: <4ba9633b-472d-4d63-9282-bd68b79fba18@acm.org> (raw)
In-Reply-To: <20241107020439.1644577-1-weilongping@oppo.com>
On 11/6/24 6:04 PM, LongPing Wei wrote:
> Call bdev_offset_from_zone_start() instead of open-coding it.
>
> Fixes: dd291d77cc90 ("block: Introduce zone write plugging")
> Signed-off-by: LongPing Wei <weilongping@oppo.com>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> ---
> v4: update commit message
> ---
> block/blk-zoned.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/blk-zoned.c b/block/blk-zoned.c
> index af19296fa50d..77a448952bbd 100644
> --- a/block/blk-zoned.c
> +++ b/block/blk-zoned.c
> @@ -537,7 +537,7 @@ static struct blk_zone_wplug *disk_get_and_lock_zone_wplug(struct gendisk *disk,
> spin_lock_init(&zwplug->lock);
> zwplug->flags = 0;
> zwplug->zone_no = zno;
> - zwplug->wp_offset = sector & (disk->queue->limits.chunk_sectors - 1);
> + zwplug->wp_offset = bdev_offset_from_zone_start(disk->part0, sector);
> bio_list_init(&zwplug->bio_list);
> INIT_WORK(&zwplug->bio_work, blk_zone_wplug_bio_work);
> zwplug->disk = disk;
Hi LongPing Wei,
Since this patch has not yet been merged, how about reposting it?
Thanks,
Bart.
next prev parent reply other threads:[~2024-12-10 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 2:04 [PATCH v4] block: get wp_offset by bdev_offset_from_zone_start LongPing Wei
2024-11-07 17:44 ` Bart Van Assche
2024-12-10 20:23 ` Bart Van Assche [this message]
2024-12-10 20:25 ` Jens Axboe
2024-12-10 20:24 ` 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=4ba9633b-472d-4d63-9282-bd68b79fba18@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@google.com \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=weilongping@oppo.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