diff options
| author | Alberto Garcia <berto@igalia.com> | 2018-08-02 17:50:23 +0300 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2018-08-15 12:50:39 +0200 |
| commit | ef7a6a3c2a7725b169d054aa7487f9738bd6c4a6 (patch) | |
| tree | 5a753c244aab646df4da696fe32c75d3a0b86126 /tests/qemu-iotests/093.out | |
| parent | f62492bb8d1ea7f7e156ffbdf411de46107072c5 (diff) | |
| download | qemu-ef7a6a3c2a7725b169d054aa7487f9738bd6c4a6.zip qemu-ef7a6a3c2a7725b169d054aa7487f9738bd6c4a6.tar.gz qemu-ef7a6a3c2a7725b169d054aa7487f9738bd6c4a6.tar.bz2 | |
qemu-iotests: Test removing a throttle group member with a pending timer
A throttle group can have several members, and each one of them can
have several pending requests in the queue.
The requests are processed in a round-robin fashion, so the algorithm
decides the drive that is going to run the next request and sets a
timer in it. Once the timer fires and the throttled request is run
then the next drive from the group is selected and a new timer is set.
If the user tried to remove a drive from a group and that drive had a
timer set then the code was not taking care of setting up a new timer
in one of the remaining members of the group, freezing their I/O.
This problem was fixed in 6fccbb475bc6effc313ee9481726a1748b6dae57,
and this patch adds a new test case that reproduces this exact
scenario.
Signed-off-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/093.out')
| -rw-r--r-- | tests/qemu-iotests/093.out | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/qemu-iotests/093.out b/tests/qemu-iotests/093.out index 594c16f..36376be 100644 --- a/tests/qemu-iotests/093.out +++ b/tests/qemu-iotests/093.out @@ -1,5 +1,5 @@ -........ +.......... ---------------------------------------------------------------------- -Ran 8 tests +Ran 10 tests OK |