diff options
author | Jenny Derzhavetz <jennyf@mellanox.com> | 2016-02-24 17:24:01 (GMT) |
---|---|---|
committer | Nicholas Bellinger <nab@linux-iscsi.org> | 2016-03-11 05:48:36 (GMT) |
commit | 6d1fba0c2cc7efe42fd761ecbba833ed0ea7b07e (patch) | |
tree | 0ce0efbd712b4cec57091609159c28d814a8ce2c /MAINTAINERS | |
parent | f81bf458208ef6d12b2fc08091204e3859dcdba4 (diff) | |
download | linux-6d1fba0c2cc7efe42fd761ecbba833ed0ea7b07e.tar.xz |
iser-target: Rework connection termination
When we receive an event that triggers connection termination,
we have a a couple of things we may want to do:
1. In case we are already terminating, bailout early
2. In case we are connected but not bound, disconnect and schedule
a connection cleanup silently (don't reinstate)
3. In case we are connected and bound, disconnect and reinstate the connection
This rework fixes a bug that was detected against a mis-behaved
initiator which rejected our rdma_cm accept, in this stage the
isert_conn is no bound and reinstate caused a bogus dereference.
What's great about this is that we don't need the
post_recv_buf_count anymore, so get rid of it.
Signed-off-by: Jenny Derzhavetz <jennyf@mellanox.com>
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Cc: stable@vger.kernel.org # v3.10+
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions