RDMA/iwcm: Don't call provider reject func with irqs disabled
authorSteve Wise <swise@opengridcomputing.com>
Wed, 7 Oct 2009 22:38:12 +0000 (15:38 -0700)
committerRoland Dreier <rolandd@cisco.com>
Wed, 7 Oct 2009 22:38:12 +0000 (15:38 -0700)
commit54e05f15ccb510c0fb3b03dfe9186811021fd5ad
tree0a3b395301d4611ca1338265d5eb68685f4d9f44
parentaa07a99412f56ad56faecbaa683f3bc0ae99abc2
RDMA/iwcm: Don't call provider reject func with irqs disabled

In commit cb58160e ("RDMA/iwcm: Reject the connection when the cm_id
is destroyed") a call to the provider's reject handler was added to
destroy_cm_id() to fix a provider endpoint leak.  This call needs to
be done with interrupts enabled.  So unlock and relock around this
call.  This is safe because:

1) the provider will do nothing with this endpoint until the iwcm either
   accepts or rejects.
2) the lock is only released after the iwcm state is changed, so an
   errant iwcm app that is destroying -and- rejecting the connection
   concurrently will get a failure on one of the calls.

Signed-off-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
drivers/infiniband/core/iwcm.c