diff options
| author | Jason Gunthorpe <jgg@nvidia.com> | 2020-09-02 11:17:08 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-11-05 11:51:12 +0100 |
| commit | 44c1c8c227b7d9cd560bb6575870aa146daae969 (patch) | |
| tree | 026224d78006133826d7553b8e9fda0e0c738e90 /include | |
| parent | d4ddc5ade2994a4df7e725c5214e36e4ea540f53 (diff) | |
| download | linux-stable-44c1c8c227b7d9cd560bb6575870aa146daae969.tar.gz linux-stable-44c1c8c227b7d9cd560bb6575870aa146daae969.tar.bz2 linux-stable-44c1c8c227b7d9cd560bb6575870aa146daae969.zip | |
RDMA/core: Change how failing destroy is handled during uobj abort
[ Upstream commit f553246f7f794675da1794ae7ee07d1f35e561ae ]
Currently it triggers a WARN_ON and then goes ahead and destroys the
uobject anyhow, leaking any driver memory.
The only place that leaks driver memory should be during FD close() in
uverbs_destroy_ufile_hw().
Drivers are only allowed to fail destroy uobjects if they guarantee
destroy will eventually succeed. uverbs_destroy_ufile_hw() provides the
loop to give the driver that chance.
Link: https://lore.kernel.org/r/20200902081708.746631-1-leon@kernel.org
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
| -rw-r--r-- | include/rdma/ib_verbs.h | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h index 5b4f0efc4241..ef7b786b8675 100644 --- a/include/rdma/ib_verbs.h +++ b/include/rdma/ib_verbs.h @@ -1463,11 +1463,6 @@ enum rdma_remove_reason { RDMA_REMOVE_DRIVER_REMOVE, /* uobj is being cleaned-up before being committed */ RDMA_REMOVE_ABORT, - /* - * uobj has been fully created, with the uobj->object set, but is being - * cleaned up before being comitted - */ - RDMA_REMOVE_ABORT_HWOBJ, }; struct ib_rdmacg_object { |