diff options
author | Kevin Wolf <kwolf@redhat.com> | 2022-12-07 14:18:29 +0100 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2022-12-15 16:08:23 +0100 |
commit | 617f3a963589dbd54fe1f323eeac36411b352a0e (patch) | |
tree | 241e42ed3cdd80a6cefa46d111df1b975f9d1312 /net/tap.c | |
parent | d9bfb9de00d4ee15908cc2f76333d6657b580dea (diff) |
test-bdrv-drain: Fix incorrrect drain assumptions
The test case assumes that a drain only happens in one specific place
where it drains explicitly. This assumption happened to hold true until
now, but block layer functions may drain interally (any graph
modifications are going to do that through bdrv_graph_wrlock()), so this
is incorrect. Make sure that the test code in .drained_begin only runs
where we actually want it to run.
When scheduling a BH from .drained_begin, we also need to increase the
in_flight counter to make sure that the operation is actually completed
in time before the node that it works on goes away.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20221207131838.239125-10-kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'net/tap.c')
0 files changed, 0 insertions, 0 deletions