From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Andreas Hindborg <nmi@metaspace.dk>
Cc: linux-block@vger.kernel.org,
Andreas Hindborg <a.hindborg@samsung.com>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
Matias Bjorling <Matias.Bjorling@wdc.com>,
Niklas Cassel <Niklas.Cassel@wdc.com>,
kernel test robot <lkp@intel.com>, Ming Lei <ming.lei@redhat.com>,
Jens Axboe <axboe@kernel.dk>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] block: ublk: enable zoned storage support
Date: Tue, 28 Feb 2023 00:20:35 +0900 [thread overview]
Message-ID: <Y/zKQx6IRirQpoIf@minwoo-desktop> (raw)
In-Reply-To: <20230224200502.391570-1-nmi@metaspace.dk>
On 23-02-24 21:05:01, Andreas Hindborg wrote:
> +static int ublk_report_zones(struct gendisk *disk, sector_t sector,
> + unsigned int nr_zones, report_zones_cb cb,
> + void *data)
> +{
> + struct ublk_device *ub;
> + unsigned int zone_size;
> + unsigned int first_zone;
> + int ret = 0;
> +
> + ub = disk->private_data;
> +
> + if (!(ub->dev_info.flags & UBLK_F_ZONED))
> + return -EINVAL;
> +
> + zone_size = disk->queue->limits.chunk_sectors;
> + first_zone = sector >> ilog2(zone_size);
> + nr_zones = min(ub->ub_disk->nr_zones - first_zone, nr_zones);
> +
> + for (unsigned int i = 0; i < nr_zones; i++) {
> + struct request *req;
> + blk_status_t status;
> + struct blk_zone info = {0};
> +
> + req = blk_mq_alloc_request(disk->queue, REQ_OP_DRV_IN, 0);
> +
> + if (IS_ERR(req)) {
> + ret = PTR_ERR(req);
> + goto out;
> + }
Can we just return directly just like above (-EINVAL)?
if (IS_ERR(req))
return PTR_ERR(req);
> +
> + req->__sector = sector;
> +
> + ret = blk_rq_map_kern(disk->queue, req, &info, sizeof(info),
> + GFP_KERNEL);
> +
> + if (ret)
> + goto out;
If we really have to use goto here, then I think we have choices:
put blk_mq_free_request(req); here or put it to the out: area.
> +
> + status = blk_execute_rq(req, 0);
> + ret = blk_status_to_errno(status);
> + if (ret)
> + goto out;
> +
> + blk_mq_free_request(req);
> +
> + ret = cb(&info, i, data);
> + if (ret)
> + goto out;
> +
> + /* A zero length zone means don't ask for more zones */
> + if (!info.len) {
> + nr_zones = i;
> + break;
> + }
> +
> + sector += zone_size;
> + }
> + ret = nr_zones;
> +
> + out:
> + return ret;
> +}
next prev parent reply other threads:[~2023-02-27 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:05 [PATCH v2] block: ublk: enable zoned storage support Andreas Hindborg
2023-02-27 10:20 ` Niklas Cassel
2023-02-27 11:59 ` Andreas Hindborg
2023-02-27 14:29 ` Niklas Cassel
2023-02-27 14:41 ` Andreas Hindborg
2023-02-27 15:20 ` Minwoo Im [this message]
2023-02-27 15:36 ` Andreas Hindborg
2023-02-28 9:52 ` Hans Holmberg
2023-03-01 7:28 ` Andreas Hindborg
2023-03-02 2:50 ` Ming Lei
2023-03-02 7:31 ` Andreas Hindborg
2023-03-02 8:19 ` Damien Le Moal
2023-03-02 8:32 ` Ming Lei
2023-03-02 9:01 ` Ming Lei
2023-03-02 9:14 ` Ming Lei
2023-03-02 10:07 ` Andreas Hindborg
2023-03-02 13:16 ` Ming Lei
2023-03-02 13:28 ` Andreas Hindborg
2023-03-03 2:59 ` Ming Lei
2023-03-03 8:27 ` Andreas Hindborg
2023-03-03 11:47 ` Ming Lei
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=Y/zKQx6IRirQpoIf@minwoo-desktop \
--to=minwoo.im.dev@gmail.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=a.hindborg@samsung.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
--cc=nmi@metaspace.dk \
/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