diff options
author | Arthur Kiyanovski <akiyano@amazon.com> | 2018-11-19 12:05:21 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-11-19 15:13:00 -0800 |
commit | 58a54b9c62e206b8d5f6e59020bcb178fc271d8e (patch) | |
tree | 4f4f3a4d564e8cdc4e4c326214269c262b210e80 /tools/perf/scripts/python | |
parent | e76ad21d070f79e566ac46ce0b0584c3c93e1b43 (diff) |
net: ena: fix crash during ena_remove()
In ena_remove() we have the following stack call:
ena_remove()
unregister_netdev()
ena_destroy_device()
netif_carrier_off()
Calling netif_carrier_off() causes linkwatch to try to handle the
link change event on the already unregistered netdev, which leads
to a read from an unreadable memory address.
This patch switches the order of the two functions, so that
netif_carrier_off() is called on a regiestered netdev.
To accomplish this fix we also had to:
1. Remove the set bit ENA_FLAG_TRIGGER_RESET
2. Add a sanitiy check in ena_close()
both to prevent double device reset (when calling unregister_netdev()
ena_close is called, but the device was already deleted in
ena_destroy_device()).
3. Set the admin_queue running state to false to avoid using it after
device was reset (for example when calling ena_destroy_all_io_queues()
right after ena_com_dev_reset() in ena_down)
Fixes: 944b28aa2982 ("net: ena: fix missing lock during device destruction")
Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions