backup fixes for 4.1?
Status from this message: Thanks, applied to my block branch:
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block/backup: deal with zero detectionblock/ blockdev.c | +10 | 5 replies | |
| 2/3 | block/backup: disable copy_range for compressed backupblock/ | +1 | 4 replies | |
| 3/3 | block/backup: refactor write_flagsblock/ | +12 | 9 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | John Snow | Max Reitz |
|---|---|---|
| 1/3 | R-b | |
| 2/3 | R-b | R-b |
| 3/3 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [Qemu-devel] [PATCH 0/3] backup fixes for 4.1?
Hi all!
Here are two small fixes.
01 is not a degradation at all, so it's OK for 4.2 02 is degradation of 3.0, so it's possibly OK for 4.2 too,
but it seems to be real bug and fix is very simple, so, may be 4.1 is better
Or you may take the whole series to 4.1 if you want.
Vladimir Sementsov-Ogievskiy (3):
block/backup: deal with zero detection block/backup: disable copy_range for compressed backup block/backup: refactor write_flags
block/backup.c | 31 ++++++++++++++----------------- blockdev.c | 8 ++++---- 2 files changed, 18 insertions(+), 21 deletions(-)
Signature · 1 line
2.18.0