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(-) -- 2.18.0
