diff options
| author | David Vrabel | 2014-07-02 17:09:15 +0200 |
|---|---|---|
| committer | David S. Miller | 2014-07-08 20:21:03 +0200 |
| commit | f9feb1e6a25f9e197f9e6e6cb04bf04d2cccff93 (patch) | |
| tree | 753ea80910d46b4cc41dd1fe1a9dbd592bb09991 /crypto | |
| parent | xen-netfront: don't nest queue locks in xennet_connect() (diff) | |
| download | kernel-qcow2-linux-f9feb1e6a25f9e197f9e6e6cb04bf04d2cccff93.tar.gz kernel-qcow2-linux-f9feb1e6a25f9e197f9e6e6cb04bf04d2cccff93.tar.xz kernel-qcow2-linux-f9feb1e6a25f9e197f9e6e6cb04bf04d2cccff93.zip | |
xen-netfront: call netif_carrier_off() only once when disconnecting
In xennet_disconnect_backend(), netif_carrier_off() was called once
per queue when it needs to only be called once.
The queue locking around the netif_carrier_off() call looked very
odd. I think they were supposed to synchronize any NAPI instances with
the expectation that no further NAPI instances would be scheduled
because of the carrier being off (see the check in
xennet_rx_interrupt()). But I can't easily tell if this works
correctly.
Instead, add a napi_synchronize() call after disabling the interrupts.
This is obviously correct as with no Rx interrupts, no further NAPI
instances will be scheduled.
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions