I think the patches speak for themselves now.

(The title of this series alludes to what the iotest added in the final
patch tests.)


v3:
- Rebased on master
- Added two tests to test-bdrv-drain [Kevin]
- Removed new iotest from auto [Thomas]


git-backport-diff against v2:

Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively

001/5:[----] [--] 'block: Keep subtree drained in drop_intermediate'
002/5:[0004] [FC] 'block: Reduce (un)drains when replacing a child'
003/5:[down] 'tests: Test polling in bdrv_drop_intermediate()'
004/5:[down] 'tests: Test mid-drain bdrv_replace_child_noperm()'
005/5:[0002] [FC] 'iotests: Add test for concurrent stream/commit'


Max Reitz (5):
  block: Keep subtree drained in drop_intermediate
  block: Reduce (un)drains when replacing a child
  tests: Test polling in bdrv_drop_intermediate()
  tests: Test mid-drain bdrv_replace_child_noperm()
  iotests: Add test for concurrent stream/commit

 block.c                    |  51 ++--
 tests/test-bdrv-drain.c    | 475 +++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/258     | 163 +++++++++++++
 tests/qemu-iotests/258.out |  33 +++
 tests/qemu-iotests/group   |   1 +
 5 files changed, 707 insertions(+), 16 deletions(-)
 create mode 100755 tests/qemu-iotests/258
 create mode 100644 tests/qemu-iotests/258.out

-- 
2.21.0

Am 22.07.2019 um 15:33 hat Max Reitz geschrieben:
> I think the patches speak for themselves now.
> 
> (The title of this series alludes to what the iotest added in the final
> patch tests.)
> 
> v3:
> - Rebased on master
> - Added two tests to test-bdrv-drain [Kevin]
> - Removed new iotest from auto [Thomas]

Thanks, applied to block-next.

Kevin