diff options
| author |   Jason Gunthorpe <jgg@nvidia.com> | 2020-07-23 10:07:06 +0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@nvidia.com> | 2020-07-29 14:10:02 -0300 |
| commit | cc9c037343898eb7a775e6b81d092ee21eeff218 (patch) | |
| tree | 5124d81370bc593ce63732db0b3e0f5eb19d922c /drivers/infiniband/core/cm.c | |
| parent | RDMA/cma: Using the standard locking pattern when delivering the removal event (diff) | |
| download | linux-dev-cc9c037343898eb7a775e6b81d092ee21eeff218.tar.xz linux-dev-cc9c037343898eb7a775e6b81d092ee21eeff218.zip | |
RDMA/cma: Remove unneeded locking for req paths
The REQ flows are concerned that once the handler is called on the new
cm_id the ULP can choose to trigger a rdma_destroy_id() concurrently at
any time.
However, this is not true, while the ULP can call rdma_destroy_id(), it
immediately blocks on the handler_mutex which prevents anything harmful
from running concurrently.
Remove the confusing extra locking and refcounts and make the
handler_mutex protecting state during destroy more clear.
Link: https://lore.kernel.org/r/20200723070707.1771101-4-leon@kernel.org
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/infiniband/core/cm.c')
0 files changed, 0 insertions, 0 deletions