diff options
| author |   Jason Gunthorpe <jgg@mellanox.com> | 2018-07-25 21:40:20 -0600 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@mellanox.com> | 2018-08-01 14:55:48 -0600 |
| commit | 0f50d88a6e9ae6d9dd14ed1a7d6b309280a9c23b (patch) | |
| tree | c0fb171864e582367f1de93f98320ec21a117465 /usr | |
| parent | IB/uverbs: Do not block disassociate during write() (diff) | |
| download | linux-dev-0f50d88a6e9ae6d9dd14ed1a7d6b309280a9c23b.tar.xz linux-dev-0f50d88a6e9ae6d9dd14ed1a7d6b309280a9c23b.zip | |
IB/uverbs: Allow all DESTROY commands to succeed after disassociate
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>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions