diff options
| author | Jason Gunthorpe <jgg@nvidia.com> | 2020-09-02 11:17:08 +0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@nvidia.com> | 2020-09-09 13:16:48 -0300 |
| commit | f553246f7f794675da1794ae7ee07d1f35e561ae (patch) | |
| tree | b278760fd3a2faf7f807b8fe1168731903406d0d /Kconfig | |
| parent | 00b3c11879d790f51cac6477abe870936a2323ae (diff) | |
| download | linux-f553246f7f794675da1794ae7ee07d1f35e561ae.tar.bz2 | |
RDMA/core: Change how failing destroy is handled during uobj abort
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>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions