summaryrefslogtreecommitdiffstats
path: root/fs/nfs/pnfs_nfs.c
diff options
context:
space:
mode:
authorDevesh Sharma2015-08-03 19:05:04 +0200
committerAnna Schumaker2015-08-05 22:22:56 +0200
commitd0f36c46deea97bd16b9277be2f1acac74d76037 (patch)
tree1c78cb9d5315bf05c43de4e49fb645e5ff085207 /fs/nfs/pnfs_nfs.c
parentcore: Remove the ib_reg_phys_mr() and ib_rereg_phys_mr() verbs (diff)
downloadkernel-qcow2-linux-d0f36c46deea97bd16b9277be2f1acac74d76037.tar.gz
kernel-qcow2-linux-d0f36c46deea97bd16b9277be2f1acac74d76037.tar.xz
kernel-qcow2-linux-d0f36c46deea97bd16b9277be2f1acac74d76037.zip
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/nfs/pnfs_nfs.c')
0 files changed, 0 insertions, 0 deletions