summaryrefslogtreecommitdiff
path: root/arch/riscv
diff options
context:
space:
mode:
authorAndrea Righi <andrea.righi@canonical.com>2020-07-24 10:59:10 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-08-05 09:59:51 +0200
commite3043abb5baad736d9255d06f8475666c8f7d649 (patch)
treea2c7072893454717e0a698bb12ae56845c64f2c7 /arch/riscv
parenta7b488d65d39d94ae66b93cca9fc655aaa2ea1bb (diff)
xen-netfront: fix potential deadlock in xennet_remove()
[ Upstream commit c2c633106453611be07821f53dff9e93a9d1c3f0 ] There's a potential race in xennet_remove(); this is what the driver is doing upon unregistering a network device: 1. state = read bus state 2. if state is not "Closed": 3. request to set state to "Closing" 4. wait for state to be set to "Closing" 5. request to set state to "Closed" 6. wait for state to be set to "Closed" If the state changes to "Closed" immediately after step 1 we are stuck forever in step 4, because the state will never go back from "Closed" to "Closing". Make sure to check also for state == "Closed" in step 4 to prevent the deadlock. Also add a 5 sec timeout any time we wait for the bus state to change, to avoid getting stuck forever in wait_event(). Signed-off-by: Andrea Righi <andrea.righi@canonical.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/riscv')
0 files changed, 0 insertions, 0 deletions