RDS: RDMA: return appropriate error on rdma map failures
authorSantosh Shilimkar <santosh.shilimkar@oracle.com>
Tue, 5 Jul 2016 00:04:37 +0000 (17:04 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 30 Nov 2017 08:39:10 +0000 (08:39 +0000)
commit5ba1957f889f575f2a240eafe543c3fda5aa72e0
tree1f82324534f739d56bae5ccddee60acb4599e1d6
parentaa85ae9db9d123c3d37645bbd491f9fe89b43ece
RDS: RDMA: return appropriate error on rdma map failures

[ Upstream commit 584a8279a44a800dea5a5c1e9d53a002e03016b4 ]

The first message to a remote node should prompt a new
connection even if it is RDMA operation. For RDMA operation
the MR mapping can fail because connections is not yet up.

Since the connection establishment is asynchronous,
we make sure the map failure because of unavailable
connection reach to the user by appropriate error code.
Before returning to the user, lets trigger the connection
so that its ready for the next retry.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/rds/send.c