Skip to content

backup fixes for 4.1?

Vladimir Sementsov-Ogievskiy qemu-devel 1 version Applied

Status from this message: Thanks, applied to my block branch:

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 22 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3block/backup: deal with zero detectionblock/backup.c blockdev.c+10 -135 replies
2/3block/backup: disable copy_range for compressed backupblock/backup.c+1 -14 replies
3/3block/backup: refactor write_flagsblock/backup.c+12 -129 replies

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchJohn SnowMax Reitz
1/3R-b
2/3R-b R-b
3/3R-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

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