> -----Original Message----- > From: Steve Wise [mailto:swise@xxxxxxxxxxxxxxxxxxxxx] > Sent: Friday, July 18, 2014 6:58 PM > To: Devesh Sharma; 'Chuck Lever' > Cc: 'Hefty, Sean'; 'Shirley Ma'; 'Roland Dreier'; linux-rdma@xxxxxxxxxxxxxxx > Subject: RE: [for-next 1/2] xprtrdma: take reference of rdma provider > module > > > > > We can't really deal with a CM_DEVICE_REMOVE event while there are > > > > active NFS mounts. > > > > > > > > System shutdown ordering should guarantee (one would hope) that > > > > NFS mount points are unmounted before the RDMA/IB core > > > > infrastructure is torn down. Ordering shouldn't matter as long all > > > > NFS activity has ceased before the CM tries to remove the device. > > > > > > > > So if something is hanging up the CM, there's something xprtrdma > > > > is not cleaning up properly. > > > > > > > > > > > > > Devesh, how are you reproducing this? Are you just rmmod'ing the > > > ocrdma module while there are active mounts? > > > > Yes, I am issuing rmmod while there is an active mount. In my case > > rmmod ocrdma remains blocked forever. > > Off-the-course of this discussion: Is there a reasoning behind not > > using > > ib_register_client()/ib_unregister_client() framework? > > I think the idea is that you don't need to use it if you are transport- > independent and use the rdmacm... Okay, Makes sense.. > > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
