cxgb4: do not call napi_hash_del()
Calling napi_hash_del() before netif_napi_del() is dangerous if a synchronize_rcu() is not enforced before NAPI struct freeing. Lets leave this detail to core networking stack and feel more comfortable. Signed-off-by: Eric Dumazet <edumazet@google.com> Cc: Hariprasad S <hariprasad@chelsio.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
ea339343d6
commit
5f00a8d8a2
1 changed files with 0 additions and 1 deletions
|
|
@ -2951,7 +2951,6 @@ void free_rspq_fl(struct adapter *adap, struct sge_rspq *rq,
|
|||
rq->cntxt_id, fl_id, 0xffff);
|
||||
dma_free_coherent(adap->pdev_dev, (rq->size + 1) * rq->iqe_len,
|
||||
rq->desc, rq->phys_addr);
|
||||
napi_hash_del(&rq->napi);
|
||||
netif_napi_del(&rq->napi);
|
||||
rq->netdev = NULL;
|
||||
rq->cntxt_id = rq->abs_id = 0;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue