2022-06-13 19:11:11

by Sergei Shtepa

[permalink] [raw]
Subject: [PATCH 15/20] block, blksnap: snapshot image block device

Provides the operation of block devices of snapshot images. Read and
write operations are redirected to the regions of difference blocks for
block device (struct diff_area).

Signed-off-by: Sergei Shtepa <[email protected]>
---
drivers/block/blksnap/snapimage.c | 345 ++++++++++++++++++++++++++++++
drivers/block/blksnap/snapimage.h | 65 ++++++
2 files changed, 410 insertions(+)
create mode 100644 drivers/block/blksnap/snapimage.c
create mode 100644 drivers/block/blksnap/snapimage.h

diff --git a/drivers/block/blksnap/snapimage.c b/drivers/block/blksnap/snapimage.c
new file mode 100644
index 000000000000..df69e989056f
--- /dev/null
+++ b/drivers/block/blksnap/snapimage.c
@@ -0,0 +1,345 @@
+// SPDX-License-Identifier: GPL-2.0
+#define pr_fmt(fmt) KBUILD_MODNAME "-snapimage: " fmt
+#include <linux/slab.h>
+#include <linux/cdrom.h>
+#include <linux/blk-mq.h>
+#include <linux/blk_snap.h>
+#ifdef CONFIG_BLK_SNAP_DEBUG_MEMORY_LEAK
+#include "memory_checker.h"
+#endif
+#include "snapimage.h"
+#include "diff_area.h"
+#include "chunk.h"
+#include "cbt_map.h"
+
+#define SNAPIMAGE_MAX_DEVICES 2048
+
+static unsigned int _major;
+static DEFINE_IDR(_minor_idr);
+static DEFINE_SPINLOCK(_minor_lock);
+
+static void free_minor(int minor)
+{
+ spin_lock(&_minor_lock);
+ idr_remove(&_minor_idr, minor);
+ spin_unlock(&_minor_lock);
+}
+
+static int new_minor(int *minor, void *ptr)
+{
+ int ret;
+
+ idr_preload(GFP_KERNEL);
+ spin_lock(&_minor_lock);
+
+ ret = idr_alloc(&_minor_idr, ptr, 0, 1 << MINORBITS, GFP_NOWAIT);
+
+ spin_unlock(&_minor_lock);
+ idr_preload_end();
+
+ if (ret < 0)
+ return ret;
+
+ *minor = ret;
+ return 0;
+}
+
+static inline void snapimage_unprepare_worker(struct snapimage *snapimage)
+{
+ kthread_flush_worker(&snapimage->worker);
+ kthread_stop(snapimage->worker_task);
+}
+
+static int snapimage_kthread_worker_fn(void *worker_ptr)
+{
+ current->flags |= PF_LOCAL_THROTTLE | PF_MEMALLOC_NOIO;
+ return kthread_worker_fn(worker_ptr);
+}
+
+static inline int snapimage_prepare_worker(struct snapimage *snapimage)
+{
+ struct task_struct *task;
+
+ kthread_init_worker(&snapimage->worker);
+
+ task = kthread_run(snapimage_kthread_worker_fn, &snapimage->worker,
+ BLK_SNAP_IMAGE_NAME "%d",
+ MINOR(snapimage->image_dev_id));
+ if (IS_ERR(task))
+ return -ENOMEM;
+
+ set_user_nice(task, MIN_NICE);
+
+ snapimage->worker_task = task;
+ return 0;
+}
+
+struct snapimage_cmd {
+ struct kthread_work work;
+};
+
+static void snapimage_queue_work(struct kthread_work *work)
+{
+ struct snapimage_cmd *cmd =
+ container_of(work, struct snapimage_cmd, work);
+ struct request *rq = blk_mq_rq_from_pdu(cmd);
+ struct snapimage *snapimage = rq->q->queuedata;
+ blk_status_t status = BLK_STS_OK;
+ struct bio_vec bvec;
+ struct req_iterator iter;
+ struct diff_area_image_ctx io_ctx;
+ sector_t pos = blk_rq_pos(rq);
+
+ diff_area_throttling_io(snapimage->diff_area);
+ diff_area_image_ctx_init(&io_ctx, snapimage->diff_area,
+ op_is_write(req_op(rq)));
+ rq_for_each_segment(bvec, rq, iter) {
+ status = diff_area_image_io(&io_ctx, &bvec, &pos);
+ if (unlikely(status != BLK_STS_OK))
+ break;
+ }
+ diff_area_image_ctx_done(&io_ctx);
+
+ blk_mq_end_request(rq, status);
+}
+
+static int snapimage_init_request(struct blk_mq_tag_set *set,
+ struct request *rq, unsigned int hctx_idx,
+ unsigned int numa_node)
+{
+ struct snapimage_cmd *cmd = blk_mq_rq_to_pdu(rq);
+
+ kthread_init_work(&cmd->work, snapimage_queue_work);
+ return 0;
+}
+
+static blk_status_t snapimage_queue_rq(struct blk_mq_hw_ctx *hctx,
+ const struct blk_mq_queue_data *bd)
+{
+ int ret;
+ struct request *rq = bd->rq;
+ struct snapimage *snapimage = rq->q->queuedata;
+ struct snapimage_cmd *cmd = blk_mq_rq_to_pdu(rq);
+
+ /*
+ * Cannot fall asleep in the context of this function,
+ * as we are under rwsem lockdown.
+ */
+
+ blk_mq_start_request(rq);
+
+ if (unlikely(!snapimage->is_ready)) {
+ blk_mq_end_request(rq, BLK_STS_IOERR);
+ return BLK_STS_IOERR;
+ }
+
+ if (op_is_write(req_op(rq))) {
+ ret = cbt_map_set_both(snapimage->cbt_map, blk_rq_pos(rq),
+ blk_rq_sectors(rq));
+ if (unlikely(ret)) {
+ blk_mq_end_request(rq, BLK_STS_IOERR);
+ return BLK_STS_IOERR;
+ }
+ }
+
+ kthread_queue_work(&snapimage->worker, &cmd->work);
+ return BLK_STS_OK;
+}
+
+static const struct blk_mq_ops mq_ops = {
+ .queue_rq = snapimage_queue_rq,
+ .init_request = snapimage_init_request,
+};
+
+const struct block_device_operations bd_ops = {
+ .owner = THIS_MODULE,
+ //.open = snapimage_open,
+ //.ioctl = snapimage_ioctl,
+ //.release = snapimage_close,
+};
+
+static inline int snapimage_alloc_tag_set(struct snapimage *snapimage)
+{
+ struct blk_mq_tag_set *set = &snapimage->tag_set;
+
+ set->ops = &mq_ops;
+ set->nr_hw_queues = 1;
+ set->nr_maps = 1;
+ set->queue_depth = 128;
+ set->numa_node = NUMA_NO_NODE;
+ set->flags = BLK_MQ_F_SHOULD_MERGE | BLK_MQ_F_STACKING;
+
+ set->cmd_size = sizeof(struct snapimage_cmd);
+ set->driver_data = snapimage;
+
+ return blk_mq_alloc_tag_set(set);
+}
+
+void snapimage_free(struct snapimage *snapimage)
+{
+ pr_info("Snapshot image disk [%u:%u] delete\n",
+ MAJOR(snapimage->image_dev_id), MINOR(snapimage->image_dev_id));
+
+ blk_mq_freeze_queue(snapimage->disk->queue);
+ snapimage->is_ready = false;
+ blk_mq_unfreeze_queue(snapimage->disk->queue);
+
+ snapimage_unprepare_worker(snapimage);
+
+ del_gendisk(snapimage->disk);
+ blk_cleanup_disk(snapimage->disk);
+ blk_mq_free_tag_set(&snapimage->tag_set);
+
+ diff_area_put(snapimage->diff_area);
+ cbt_map_put(snapimage->cbt_map);
+
+ free_minor(MINOR(snapimage->image_dev_id));
+ kfree(snapimage);
+#ifdef CONFIG_BLK_SNAP_DEBUG_MEMORY_LEAK
+ memory_object_dec(memory_object_snapimage);
+#endif
+}
+
+struct snapimage *snapimage_create(struct diff_area *diff_area,
+ struct cbt_map *cbt_map)
+{
+ int ret = 0;
+ int minor;
+ struct snapimage *snapimage = NULL;
+ struct gendisk *disk;
+
+ pr_info("Create snapshot image for device [%u:%u]\n",
+ MAJOR(diff_area->orig_bdev->bd_dev),
+ MINOR(diff_area->orig_bdev->bd_dev));
+
+ snapimage = kzalloc(sizeof(struct snapimage), GFP_KERNEL);
+ if (snapimage == NULL)
+ return ERR_PTR(-ENOMEM);
+#ifdef CONFIG_BLK_SNAP_DEBUG_MEMORY_LEAK
+ memory_object_inc(memory_object_snapimage);
+#endif
+ ret = new_minor(&minor, snapimage);
+ if (ret) {
+ pr_err("Failed to allocate minor for snapshot image device. errno=%d\n",
+ abs(ret));
+ goto fail_free_image;
+ }
+
+ snapimage->is_ready = true;
+ snapimage->capacity = cbt_map->device_capacity;
+ snapimage->image_dev_id = MKDEV(_major, minor);
+ pr_info("Snapshot image device id [%u:%u]\n",
+ MAJOR(snapimage->image_dev_id), MINOR(snapimage->image_dev_id));
+
+ ret = snapimage_prepare_worker(snapimage);
+ if (ret) {
+ pr_err("Failed to prepare worker thread. errno=%d\n", abs(ret));
+ goto fail_free_minor;
+ }
+
+ ret = snapimage_alloc_tag_set(snapimage);
+ if (ret) {
+ pr_err("Failed to allocate tag set. errno=%d\n", abs(ret));
+ goto fail_free_worker;
+ }
+
+ disk = blk_mq_alloc_disk(&snapimage->tag_set, snapimage);
+ if (IS_ERR(disk)) {
+ ret = PTR_ERR(disk);
+ pr_err("Failed to allocate disk. errno=%d\n", abs(ret));
+ goto fail_free_tagset;
+ }
+
+ blk_queue_max_hw_sectors(disk->queue, BLK_DEF_MAX_SECTORS);
+ blk_queue_flag_set(QUEUE_FLAG_NOMERGES, disk->queue);
+
+ if (snprintf(disk->disk_name, DISK_NAME_LEN, "%s%d",
+ BLK_SNAP_IMAGE_NAME, minor) < 0) {
+ pr_err("Unable to set disk name for snapshot image device: invalid minor %u\n",
+ minor);
+ ret = -EINVAL;
+ goto fail_cleanup_disk;
+ }
+ pr_info("Snapshot image disk name [%s]\n", disk->disk_name);
+
+ disk->flags = 0;
+ //disk->flags |= GENHD_FL_HIDDEN;
+ //disk->flags |= GENHD_FL_REMOVABLE;
+#ifdef GENHD_FL_NO_PART_SCAN
+ disk->flags |= GENHD_FL_NO_PART_SCAN;
+#else
+ disk->flags |= GENHD_FL_NO_PART;
+#endif
+
+
+ disk->major = _major;
+ disk->first_minor = minor;
+ disk->minors = 1; // One disk has only one partition.
+
+ disk->fops = &bd_ops;
+ disk->private_data = snapimage;
+ snapimage->disk = disk;
+
+ set_capacity(disk, snapimage->capacity);
+ pr_debug("Snapshot image device capacity %lld bytes\n",
+ (u64)(snapimage->capacity << SECTOR_SHIFT));
+
+ diff_area_get(diff_area);
+ snapimage->diff_area = diff_area;
+ cbt_map_get(cbt_map);
+ snapimage->cbt_map = cbt_map;
+
+ ret = add_disk(disk);
+ if (ret) {
+ pr_err("Failed to add disk [%s] for snapshot image device\n",
+ disk->disk_name);
+ goto fail_cleanup_disk;
+ }
+
+ return snapimage;
+
+fail_cleanup_disk:
+ blk_cleanup_disk(disk);
+fail_free_tagset:
+ blk_mq_free_tag_set(&snapimage->tag_set);
+fail_free_worker:
+ snapimage_unprepare_worker(snapimage);
+fail_free_minor:
+ free_minor(minor);
+fail_free_image:
+ kfree(snapimage);
+#ifdef CONFIG_BLK_SNAP_DEBUG_MEMORY_LEAK
+ memory_object_dec(memory_object_snapimage);
+#endif
+ return ERR_PTR(ret);
+}
+
+int snapimage_init(void)
+{
+ int mj = 0;
+
+ mj = register_blkdev(mj, BLK_SNAP_IMAGE_NAME);
+ if (mj < 0) {
+ pr_err("Failed to register snapshot image block device. errno=%d\n",
+ abs(mj));
+ return mj;
+ }
+ _major = mj;
+ pr_info("Snapshot image block device major %d was registered\n",
+ _major);
+
+ return 0;
+}
+
+void snapimage_done(void)
+{
+ unregister_blkdev(_major, BLK_SNAP_IMAGE_NAME);
+ pr_info("Snapshot image block device [%d] was unregistered\n", _major);
+
+ idr_destroy(&_minor_idr);
+}
+
+int snapimage_major(void)
+{
+ return _major;
+}
diff --git a/drivers/block/blksnap/snapimage.h b/drivers/block/blksnap/snapimage.h
new file mode 100644
index 000000000000..e978711004f0
--- /dev/null
+++ b/drivers/block/blksnap/snapimage.h
@@ -0,0 +1,65 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#pragma once
+#include <linux/blk_types.h>
+#include <linux/blkdev.h>
+#include <linux/blk-mq.h>
+#include <linux/kthread.h>
+
+struct diff_area;
+struct cbt_map;
+
+/**
+ * struct snapimage - Snapshot image block device.
+ *
+ * @image_dev_id:
+ * ID of the snapshot image block device.
+ * @capacity:
+ * The size of the snapshot image in sectors must be equal to the size
+ * of the original device at the time of taking the snapshot.
+ * @is_ready:
+ * The flag means that the snapshot image is ready for processing
+ * I/O requests.
+ * @worker:
+ * The worker thread for processing I/O requests.
+ * @worker_task:
+ * A pointer to the &struct task of the worker thread.
+ * @tag_set:
+ * Area to keep a shared tag map.
+ * @disk:
+ * A pointer to the &struct gendisk for the image block device.
+ * @diff_area:
+ * A pointer to the owned &struct diff_area.
+ * @cbt_map:
+ * A pointer to the owned &struct cbt_map.
+ *
+ * The snapshot image is presented in the system as a block device. But
+ * when reading or writing a snapshot image, the data is redirected to
+ * the original block device or to the block device of the difference storage.
+ *
+ * The module does not prohibit reading and writing data to the snapshot
+ * from different threads in parallel. To avoid the problem with simultaneous
+ * access, it is enough to open the snapshot image block device with the
+ * FMODE_EXCL parameter.
+ */
+struct snapimage {
+ dev_t image_dev_id;
+ sector_t capacity;
+ bool is_ready;
+
+ struct kthread_worker worker;
+ struct task_struct *worker_task;
+
+ struct blk_mq_tag_set tag_set;
+ struct gendisk *disk;
+
+ struct diff_area *diff_area;
+ struct cbt_map *cbt_map;
+};
+
+int snapimage_init(void);
+void snapimage_done(void);
+int snapimage_major(void);
+
+void snapimage_free(struct snapimage *snapimage);
+struct snapimage *snapimage_create(struct diff_area *diff_area,
+ struct cbt_map *cbt_map);
--
2.20.1


2022-07-06 13:18:47

by Christoph Hellwig

[permalink] [raw]
Subject: Re: [PATCH 15/20] block, blksnap: snapshot image block device

> +#include <linux/cdrom.h>

What do you need this for?

> +static int new_minor(int *minor, void *ptr)
> +{
> + int ret;
> +
> + idr_preload(GFP_KERNEL);
> + spin_lock(&_minor_lock);
> +
> + ret = idr_alloc(&_minor_idr, ptr, 0, 1 << MINORBITS, GFP_NOWAIT);
> +
> + spin_unlock(&_minor_lock);
> + idr_preload_end();
> +
> + if (ret < 0)
> + return ret;
> +
> + *minor = ret;
> + return 0;
> +}

alloc_disk not automatically allocates minors for you if you don't
set the ->major and ->first_minor fields, which could simply this
a lot.

> +static int snapimage_init_request(struct blk_mq_tag_set *set,
> + struct request *rq, unsigned int hctx_idx,
> + unsigned int numa_node)
> +{
> + struct snapimage_cmd *cmd = blk_mq_rq_to_pdu(rq);
> +
> + kthread_init_work(&cmd->work, snapimage_queue_work);
> + return 0;
> +}

I'm a little confused on why this both has a blk-mq interface and
the new bio filter interface. Whow is going to submit I/O to this
blk-mq interface?

> + //.open = snapimage_open,
> + //.ioctl = snapimage_ioctl,
> + //.release = snapimage_close,

Please don't leave commented out code around.

2022-07-07 09:43:54

by Sergei Shtepa

[permalink] [raw]
Subject: Re: [PATCH 15/20] block, blksnap: snapshot image block device


>
>> +static int snapimage_init_request(struct blk_mq_tag_set *set,
>> + struct request *rq, unsigned int hctx_idx,
>> + unsigned int numa_node)
>> +{
>> + struct snapimage_cmd *cmd = blk_mq_rq_to_pdu(rq);
>> +
>> + kthread_init_work(&cmd->work, snapimage_queue_work);
>> + return 0;
>> +}
> I'm a little confused on why this both has a blk-mq interface and
> the new bio filter interface. Whow is going to submit I/O to this
> blk-mq interface?
>

Sorry, it seems to me that I didn't understand this comment.

The module creates a block device for each snapshot image.
To make a backup of a block device, the backup tool reads snapshot image.
This snapshot image block device allows to mount a file system on it
and perform the necessary preparation. If not for this requirement,
it would be possible to implement reading via an additional ioctl.
But that wouldn't be a good design, I think.

Perhaps I have implemented this block device incorrectly?
Processing requests of the snapshot image block device is started
in the function snapimage_queue_rq(). And ends in the
snapimage_queue_work() in another kernel thread. Therefore, when
the request is initialized in snapimage_init_request(), a kernel worker
is prepared.

>> + //.open = snapimage_open,
>> + //.ioctl = snapimage_ioctl,
>> + //.release = snapimage_close,
> Please don't leave commented out code around.
>

2022-07-07 17:29:10

by Christoph Hellwig

[permalink] [raw]
Subject: Re: [PATCH 15/20] block, blksnap: snapshot image block device

On Thu, Jul 07, 2022 at 11:16:42AM +0200, Sergei Shtepa wrote:
> The module creates a block device for each snapshot image.
> To make a backup of a block device, the backup tool reads snapshot image.
> This snapshot image block device allows to mount a file system on it
> and perform the necessary preparation. If not for this requirement,
> it would be possible to implement reading via an additional ioctl.
> But that wouldn't be a good design, I think.

Ok, got it. It was just me who was confused.

>
> Perhaps I have implemented this block device incorrectly?
> Processing requests of the snapshot image block device is started
> in the function snapimage_queue_rq(). And ends in the
> snapimage_queue_work() in another kernel thread. Therefore, when
> the request is initialized in snapimage_init_request(), a kernel worker
> is prepared.

I don't think it is wrong, but there is some potential for optimization.

Is there a reson this is implemented as a blk-mq driver vs a bio
based driver that just implements ->submit_bio? The latter has
the advantage that you are always called in user context, and don't
need the extra workqueue offload.

The block layer also generally assumes that blk-mq drivers don't
call submit_bio_noacct underneath, so if we can't I'd much
prefer the bio based driver approach here.

2022-07-08 08:03:28

by Sergei Shtepa

[permalink] [raw]
Subject: Re: [PATCH 15/20] block, blksnap: snapshot image block device


> On Thu, Jul 07, 2022 at 11:16:42AM +0200, Sergei Shtepa wrote:
>> The module creates a block device for each snapshot image.
>> To make a backup of a block device, the backup tool reads snapshot image.
>> This snapshot image block device allows to mount a file system on it
>> and perform the necessary preparation. If not for this requirement,
>> it would be possible to implement reading via an additional ioctl.
>> But that wouldn't be a good design, I think.
> Ok, got it. It was just me who was confused.
>
>> Perhaps I have implemented this block device incorrectly?
>> Processing requests of the snapshot image block device is started
>> in the function snapimage_queue_rq(). And ends in the
>> snapimage_queue_work() in another kernel thread. Therefore, when
>> the request is initialized in snapimage_init_request(), a kernel worker
>> is prepared.
> I don't think it is wrong, but there is some potential for optimization.
>
> Is there a reson this is implemented as a blk-mq driver vs a bio
> based driver that just implements ->submit_bio? The latter has
> the advantage that you are always called in user context, and don't
> need the extra workqueue offload.
>
> The block layer also generally assumes that blk-mq drivers don't
> call submit_bio_noacct underneath, so if we can't I'd much
> prefer the bio based driver approach here.
>

There was a goal to use the kernel innovations whenever possible.
Of course, it makes sense to return to bio based if it allows to
achieve better performance. This is not a matter of principle.

2022-07-08 08:18:03

by Christoph Hellwig

[permalink] [raw]
Subject: Re: [PATCH 15/20] block, blksnap: snapshot image block device

On Fri, Jul 08, 2022 at 09:58:25AM +0200, Sergei Shtepa wrote:
> There was a goal to use the kernel innovations whenever possible.
> Of course, it makes sense to return to bio based if it allows to
> achieve better performance. This is not a matter of principle.

In general blk-mq is designed for hardware drivers, while the
bio based interface is for stacking drivers. There are some
exceptions: dm-mpath is a stacking blk-mq driver, but one that
just passes I/O through, and there is a bunch of hardware drivers
implemented as bio based ones, although I suspect most of them
would end up being improved by switching to blk-mq (or in most
case by just deleting them).