From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@oracle.com>
Subject: [net-next][PATCH v3 09/13] RDS: IB: handle the RDMA CM time wait event
Date: Tue, 1 Mar 2016 15:20:50 -0800 [thread overview]
Message-ID: <1456874454-10355-10-git-send-email-santosh.shilimkar@oracle.com> (raw)
In-Reply-To: <1456874454-10355-1-git-send-email-santosh.shilimkar@oracle.com>
Drop the RDS connection on RDMA_CM_EVENT_TIMEWAIT_EXIT so that
it can reconnect and resume.
While testing fastreg, this error happened in couple of tests but
was getting un-noticed.
Signed-off-by: Santosh Shilimkar <ssantosh@kernel.org>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
---
net/rds/rdma_transport.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/net/rds/rdma_transport.c b/net/rds/rdma_transport.c
index 4f4b3d8..7220beb 100644
--- a/net/rds/rdma_transport.c
+++ b/net/rds/rdma_transport.c
@@ -117,6 +117,14 @@ int rds_rdma_cm_event_handler(struct rdma_cm_id *cm_id,
rds_conn_drop(conn);
break;
+ case RDMA_CM_EVENT_TIMEWAIT_EXIT:
+ if (conn) {
+ pr_info("RDS: RDMA_CM_EVENT_TIMEWAIT_EXIT event: dropping connection %pI4->%pI4\n",
+ &conn->c_laddr, &conn->c_faddr);
+ rds_conn_drop(conn);
+ }
+ break;
+
default:
/* things like device disconnect? */
printk(KERN_ERR "RDS: unknown event %u (%s)!\n",
--
1.9.1
next prev parent reply other threads:[~2016-03-01 23:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 23:20 RDS: Major clean-up with couple of new features for 4.6 Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 01/13] RDS: Drop stale iWARP RDMA transport Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 03/13] MAINTAINERS: update RDS entry Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 05/13] RDS: IB: Re-organise ibmr code Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 06/13] RDS: IB: create struct rds_ib_fmr Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 07/13] RDS: IB: move FMR code to its own file Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 08/13] RDS: IB: add connection info to ibmr Santosh Shilimkar
2016-03-01 23:20 ` Santosh Shilimkar [this message]
2016-03-01 23:20 ` [net-next][PATCH v3 10/13] RDS: IB: add mr reused stats Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 11/13] RDS: IB: add Fastreg MR (FRMR) detection support Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 12/13] RDS: IB: allocate extra space on queues for FRMR support Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode Santosh Shilimkar
2016-03-02 19:13 ` RDS: Major clean-up with couple of new features for 4.6 David Miller
2016-03-02 19:15 ` santosh shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456874454-10355-10-git-send-email-santosh.shilimkar@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).