diff options
author | Jason Gunthorpe <jgg@nvidia.com> | 2020-07-23 10:07:04 +0300 |
---|---|---|
committer | Jason Gunthorpe <jgg@nvidia.com> | 2020-07-29 20:10:01 +0300 |
commit | d54f23c09ec62670901f1a2a4712a5218522ca2b (patch) | |
tree | 130ce7ad5538758d052cedb29c53704d8a5d1f4c /drivers/scsi/3w-xxxx.c | |
parent | d4f9cb5c5b224dca3ff752c1bb854250bf114944 (diff) | |
download | linux-d54f23c09ec62670901f1a2a4712a5218522ca2b.tar.xz |
RDMA/cma: Simplify DEVICE_REMOVAL for internal_id
cma_process_remove() triggers an unconditional rdma_destroy_id() for
internal_id's and skips the event deliver and transition through
RDMA_CM_DEVICE_REMOVAL.
This is confusing and unnecessary. internal_id always has
cma_listen_handler() as the handler, have it catch the
RDMA_CM_DEVICE_REMOVAL event and directly consume it and signal removal.
This way the FSM sequence never skips the DEVICE_REMOVAL case and the
logic in this hard to test area is simplified.
Link: https://lore.kernel.org/r/20200723070707.1771101-2-leon@kernel.org
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/scsi/3w-xxxx.c')
0 files changed, 0 insertions, 0 deletions