IB/uverbs: Allow all DESTROY commands to succeed after disassociate

Browse source

The disassociate function was broken by design because it failed all
commands. This prevents userspace from calling destroy on a uobject after
it has detected a device fatal error and thus reclaiming the resources in
userspace is prevented.

This fix is now straightforward, when anything destroys a uobject that is
not the user the object remains on the IDR with a NULL context and object
pointer. All lookup locking modes other than DESTROY will fail. When the
user ultimately calls the destroy function it is simply dropped from the
IDR while any related information is returned.

Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>

...

This commit is contained in:

Jason Gunthorpe 2018-07-25 21:40:20 -06:00

parent a9b66d6453

commit 0f50d88a6e

4 changed files with 66 additions and 16 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

66

drivers/infiniband/core/rdma_core.c

View file

3

drivers/infiniband/core/rdma_core.h

View file

7

drivers/infiniband/core/uverbs_main.c

View file

6

include/rdma/uverbs_types.h

View file