summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeon Romanovsky <leonro@mellanox.com>2017-07-23 09:46:14 +0200
committerLeon Romanovsky <leonro@mellanox.com>2017-07-23 09:52:00 +0200
commitb287b76e89503ef1d403cc5cc8bd74b035d25bfa (patch)
treea4bb1bcda59ba4f9cb55947cbaaa9ca640f4dca7
parentIB/ipoib: Remove double pointer assigning (diff)
downloadlinux-b287b76e89503ef1d403cc5cc8bd74b035d25bfa.tar.xz
linux-b287b76e89503ef1d403cc5cc8bd74b035d25bfa.zip
Revert "IB/core: Allow QP state transition from reset to error"
The commit ebc9ca43e1d5 ("IB/core: Allow QP state transition from reset to error") allowed transition from Reset to Error state for the QPs. This behavior doesn't follow the IBTA specification 1.3, which in 10.3.1 QUEUE PAIR AND EE CONTEXT STATES section. The quote from the spec: "An error can be forced from any state, except Reset, with the Modify QP/EE Verb." Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
-rw-r--r--drivers/infiniband/core/verbs.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/infiniband/core/verbs.c b/drivers/infiniband/core/verbs.c
index fb98ed67d5bc..7f8fe443df46 100644
--- a/drivers/infiniband/core/verbs.c
+++ b/drivers/infiniband/core/verbs.c
@@ -895,7 +895,6 @@ static const struct {
} qp_state_table[IB_QPS_ERR + 1][IB_QPS_ERR + 1] = {
[IB_QPS_RESET] = {
[IB_QPS_RESET] = { .valid = 1 },
- [IB_QPS_ERR] = { .valid = 1 },
[IB_QPS_INIT] = {
.valid = 1,
.req_param = {