diff options
author | Devesh Sharma <devesh.sharma@avagotech.com> | 2015-08-03 13:05:04 -0400 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2015-08-05 16:22:56 -0400 |
commit | d0f36c46deea97bd16b9277be2f1acac74d76037 (patch) | |
tree | 1c78cb9d5315bf05c43de4e49fb645e5ff085207 /fs/ext4 | |
parent | 1241d7bf2ac8838d0d2d0b54a6173ac3eb3747a4 (diff) | |
download | linux-d0f36c46deea97bd16b9277be2f1acac74d76037.tar.bz2 |
xprtrdma: take HCA driver refcount at client
This is a rework of the following patch sent almost a year back:
http://www.mail-archive.com/linux-rdma%40vger.kernel.org/msg20730.html
In presence of active mount if someone tries to rmmod vendor-driver, the
command remains stuck forever waiting for destruction of all rdma-cm-id.
in worst case client can crash during shutdown with active mounts.
The existing code assumes that ia->ri_id->device cannot change during
the lifetime of a transport. xprtrdma do not have support for
DEVICE_REMOVAL event either. Lifting that assumption and adding support
for DEVICE_REMOVAL event is a long chain of work, and is in plan.
The community decided that preventing the hang right now is more
important than waiting for architectural changes.
Thus, this patch introduces a temporary workaround to acquire HCA driver
module reference count during the mount of a nfs-rdma mount point.
Signed-off-by: Devesh Sharma <devesh.sharma@avagotech.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Sagi Grimberg <sagig@dev.mellanox.co.il>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs/ext4')
0 files changed, 0 insertions, 0 deletions