[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-block] [PATCH 0/3] potentially broken drive-mirror/drive-backup in
|
From: |
Denis V. Lunev |
|
Subject: |
[Qemu-block] [PATCH 0/3] potentially broken drive-mirror/drive-backup in bdrv_co_discard |
|
Date: |
Thu, 16 Jun 2016 09:58:04 +0300 |
Actually I have found this problem running iotest 132 for active async
mirror I have sent yesturday. Anyway, the problem is actual for current
backup/mirror implementation.
bdrv_co_discard must mark areas dirty after writing zeroes, it must call
before_write_notifier chain to push underlying data to backup and it also
must properly fill tracked request information.
Signed-off-by: Denis V. Lunev <address@hidden>
CC: Vladimir Sementsov-Ogievskiy<address@hidden>
CC: Stefan Hajnoczi <address@hidden>
CC: Fam Zheng <address@hidden>
CC: Kevin Wolf <address@hidden>
CC: Max Reitz <address@hidden>
- [Qemu-block] [PATCH 0/3] potentially broken drive-mirror/drive-backup in bdrv_co_discard,
Denis V. Lunev <=