diff options
| author | Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com> | 2026-05-19 20:30:38 +0530 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@nvidia.com> | 2026-05-24 12:32:21 -0300 |
| commit | 73607410f4f1b0d5c3d0af2d70a79c265482a0e3 (patch) | |
| tree | 0d4131d4e0568c0d1dd3f73867620f79e7621063 /drivers/android/binder/range_alloc/array.rs | |
| parent | c35b5fcc4ce81a1850d9d5bf9d616a7e2d69308e (diff) | |
RDMA/bnxt_re: Enhance dbr usecnt logic in doorbell uapis
The current logic in the doorbell cleanup function is not
sufficient for a change in a subsequent patch, that fails
doorbell remove operation in some conditions. The cleanup
should facilitate freeing of the dbr object when the caller
may not retry the teardown operation (implicit teardown:
process-exit/driver-removal).
Extend this counter to use kref mechanism so that the dbr
object gets freed (via kref callback) when there are no more
references to it, rather than directly freeing it in the
cleanup uapi.
Link: https://patch.msgid.link/r/20260519150041.7251-7-sriharsha.basavapatna@broadcom.com
Signed-off-by: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Reviewed-by: Selvin Xavier <selvin.xavier@broadcom.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/android/binder/range_alloc/array.rs')
0 files changed, 0 insertions, 0 deletions
