diff options
author | Raju Rangoju <rajur@chelsio.com> | 2017-06-19 19:46:00 +0530 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-06-19 10:59:04 -0400 |
commit | dec6b33163d24e2c19ba521c89fffbaab53ae986 (patch) | |
tree | 29de6750ddbcfcc2ddaf14bb1536db98cc8385e3 /net/8021q | |
parent | 4b153ca989a9bf61f622ded32e1d689df88edaa5 (diff) | |
download | linux-stable-dec6b33163d24e2c19ba521c89fffbaab53ae986.tar.gz linux-stable-dec6b33163d24e2c19ba521c89fffbaab53ae986.tar.bz2 linux-stable-dec6b33163d24e2c19ba521c89fffbaab53ae986.zip |
cxgb4: notify uP to route ctrlq compl to rdma rspq
During the module initialisation there is a possible race
(basically race between uld and lld) where neither the uld
nor lld notifies the uP about where to route the ctrl queue
completions. LLD skips notifying uP as the rdma queues were
not created by then (will leave it to ULD to notify the uP).
As the ULD comes up, it also skips notifying the uP as the
flag FULL_INIT_DONE is not set yet (ULD assumes that the
interface is not up yet).
Consequently, this race between uld and lld leaves uP
unnotified about where to send the ctrl queue completions
to, leading to iwarp RI_RES WR failure.
Here is the race:
CPU 0 CPU1
- allocates nic rx queus
- t4_sge_alloc_ctrl_txq()
(if rdma rsp queues exists,
tell uP to route ctrl queue
compl to rdma rspq)
- acquires the mutex_lock
- allocates rdma response queues
- if FULL_INIT_DONE set,
tell uP to route ctrl queue compl
to rdma rspq
- relinquishes mutex_lock
- acquires the mutex_lock
- enable_rx()
- set FULL_INIT_DONE
- relinquishes mutex_lock
This patch fixes the above issue.
Fixes: e7519f9926f1('cxgb4: avoid enabling napi twice to the same queue')
Signed-off-by: Raju Rangoju <rajur@chelsio.com>
Acked-by: Steve Wise <swise@opengridcomputing.com>
CC: Stable <stable@vger.kernel.org> # 4.9+
Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/8021q')
0 files changed, 0 insertions, 0 deletions