On 12/2/2014 3:30 AM, Greg KH wrote:
On Mon, Dec 01, 2014 at 07:49:56PM +0200, Sagi Grimberg wrote:
ISER_CONN_UP state is not sufficient to know if
we should wait for completion of flush errors and
disconnected_handler event.
Instead, split it to 2 states:
- ISER_CONN_UP: Got to CM connected phase, This state
indicates that we need to wait for a CM disconnect
event before going to teardown.
- ISER_CONN_FULL_FEATURE: Got to full feature phase
after we posted login response, This state indicates
that we posted recv buffers and we need to wait for
flush completions before going to teardown.
Cc: <stable@xxxxxxxxxxxxxxx> # 3.10+
Signed-off-by: Sagi Grimberg <sagig@xxxxxxxxxxxx>
---
drivers/infiniband/ulp/isert/ib_isert.c | 29 ++++++++++++++++++++++++-----
drivers/infiniband/ulp/isert/ib_isert.h | 1 +
2 files changed, 25 insertions(+), 5 deletions(-)
Any reason you sent out 3 copies of this patch series?
Yes, but a dumb one. Sorry about that...
And please go read Documentation/stable_kernel_rules.txt, I don't think
many of these patches in this series are actually relevant for stable
kernels.
While some of these patches may not seem directly as a bug fix, when
combined together, they fix several BUG prone flows.
Please discard these patches, and Nic and I will rework those soon.
Sorry for the hassle Greg.
Sagi.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html