[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v5 1/4] block/io: fix copy_range
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] [PATCH v5 1/4] block/io: fix copy_range |
Date: |
Tue, 10 Jul 2018 09:49:35 +0800 |
User-agent: |
Mutt/1.10.0 (2018-05-17) |
On Mon, 07/09 19:37, Vladimir Sementsov-Ogievskiy wrote:
> Here two things are fixed:
>
> 1. Architecture
>
> On each recursion step, we go to the child of src or dst, only for one
> of them. So, it's wrong to create tracked requests for both on each
> step. It leads to tracked requests duplication.
>
> 2. Wait for serializing requests on write path independently of
> BDRV_REQ_NO_SERIALISING
>
> Before commit 9ded4a01149 "backup: Use copy offloading",
> BDRV_REQ_NO_SERIALISING was used for only one case: read in
> copy-on-write operation during backup. Also, the flag was handled only
> on read path (in bdrv_co_preadv and bdrv_aligned_preadv).
>
> After 9ded4a01149, flag is used for not waiting serializing operations
> on backup target (in same case of copy-on-write operation). This
> behavior change is unsubstantiated and potentially dangerous, let's
> drop it and add additional asserts and documentation.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Reviewed-by: Fam Zheng <address@hidden>
- [Qemu-devel] [PATCH v5 0/4] fix image fleecing, Vladimir Sementsov-Ogievskiy, 2018/07/09
- [Qemu-devel] [PATCH v5 4/4] block/backup: fix fleecing scheme: use serialized writes, Vladimir Sementsov-Ogievskiy, 2018/07/09
- [Qemu-devel] [PATCH v5 3/4] block: add BDRV_REQ_SERIALISING flag, Vladimir Sementsov-Ogievskiy, 2018/07/09
- [Qemu-devel] [PATCH v5 1/4] block/io: fix copy_range, Vladimir Sementsov-Ogievskiy, 2018/07/09
- Re: [Qemu-devel] [PATCH v5 1/4] block/io: fix copy_range,
Fam Zheng <=
- [Qemu-devel] [PATCH v5 2/4] block: split flags in copy_range, Vladimir Sementsov-Ogievskiy, 2018/07/09
- Re: [Qemu-devel] [PATCH v5 0/4] fix image fleecing, Kevin Wolf, 2018/07/10