Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

enic: prevent waking up stopped tx queues over watchdog reset

Recent months, our customer reported several kernel crashes all
preceding with following message:
NETDEV WATCHDOG: eth2 (enic): transmit queue 0 timed out
Error message of one of those crashes:
BUG: unable to handle kernel paging request at ffffffffa007e090

After analyzing severl vmcores, I found that most of crashes are
caused by memory corruption. And all the corrupted memory areas
are overwritten by data of network packets. Moreover, I also found
that the tx queues were enabled over watchdog reset.

After going through the source code, I found that in enic_stop(),
the tx queues stopped by netif_tx_disable() could be woken up over
a small time window between netif_tx_disable() and the
napi_disable() by the following code path:
napi_poll->
enic_poll_msix_wq->
vnic_cq_service->
enic_wq_service->
netif_wake_subqueue(enic->netdev, q_number)->
test_and_clear_bit(__QUEUE_STATE_DRV_XOFF, &txq->state)
In turn, upper netowrk stack could queue skb to ENIC NIC though
enic_hard_start_xmit(). And this might introduce some race condition.

Our customer comfirmed that this kind of kernel crash doesn't occur over
90 days since they applied this patch.

Signed-off-by: Firo Yang <firo.yang@suse.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by

Firo Yang and committed by
David S. Miller
0f905225 b44beb8a

+1 -1
+1 -1
drivers/net/ethernet/cisco/enic/enic_main.c
··· 2013 2013 napi_disable(&enic->napi[i]); 2014 2014 2015 2015 netif_carrier_off(netdev); 2016 - netif_tx_disable(netdev); 2017 2016 if (vnic_dev_get_intr_mode(enic->vdev) == VNIC_DEV_INTR_MODE_MSIX) 2018 2017 for (i = 0; i < enic->wq_count; i++) 2019 2018 napi_disable(&enic->napi[enic_cq_wq(enic, i)]); 2019 + netif_tx_disable(netdev); 2020 2020 2021 2021 if (!enic_is_dynamic(enic) && !enic_is_sriov_vf(enic)) 2022 2022 enic_dev_del_station_addr(enic);