diff options
| author | Netanel Belgazal <netanel@amazon.com> | 2017-11-19 21:03:40 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-11-20 05:35:16 +0300 |
| commit | d18e4f6834451dbc12407c26acd5fae4da14c489 (patch) | |
| tree | 4a0c4bd707bf32ee2b72f6574906b4847bebbb51 /drivers/net/ethernet/amazon/ena/ena_netdev.h | |
| parent | b399a3944d53fb8f39b202da9830e8daa1336e19 (diff) | |
| download | linux-d18e4f6834451dbc12407c26acd5fae4da14c489.tar.xz | |
net: ena: fix race condition between device reset and link up setup
In rare cases, ena driver would reset and re-start the device,
for example, in case of misbehaving application that causes
transmit timeout
The first step in the reset procedure is to stop the Tx traffic by
calling ena_carrier_off().
After the driver have just started the device reset procedure, device
happens to send an asynchronous notification (via AENQ) to the driver
than there was a link change (to link-up state).
This link change is mapped to a call to netif_carrier_on() which
re-activates the Tx queues, violating the assumption of no tx traffic
until device reset is completed, as the reset task might still be in
the process of queues initialization, leading to an access to
uninitialized memory.
Signed-off-by: Netanel Belgazal <netanel@amazon.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/amazon/ena/ena_netdev.h')
| -rw-r--r-- | drivers/net/ethernet/amazon/ena/ena_netdev.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/net/ethernet/amazon/ena/ena_netdev.h b/drivers/net/ethernet/amazon/ena/ena_netdev.h index ed8bd0a579c4..3bbc003871de 100644 --- a/drivers/net/ethernet/amazon/ena/ena_netdev.h +++ b/drivers/net/ethernet/amazon/ena/ena_netdev.h @@ -272,7 +272,8 @@ enum ena_flags_t { ENA_FLAG_DEV_UP, ENA_FLAG_LINK_UP, ENA_FLAG_MSIX_ENABLED, - ENA_FLAG_TRIGGER_RESET + ENA_FLAG_TRIGGER_RESET, + ENA_FLAG_ONGOING_RESET }; /* adapter specific private data structure */ |