diff options
| author | Jason Gunthorpe <[email protected]> | 2020-05-07 06:33:47 +0000 |
|---|---|---|
| committer | Jason Gunthorpe <[email protected]> | 2020-05-12 20:02:25 +0000 |
| commit | c485b19d52c4ba269dfd027945dee81755fdd530 (patch) | |
| tree | 2e47f16c2ca83db8d43bd403dce1e4e066f7f95c /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | RDMA/iw_cxgb4: Fix incorrect function parameters (diff) | |
| download | kernel-c485b19d52c4ba269dfd027945dee81755fdd530.tar.gz kernel-c485b19d52c4ba269dfd027945dee81755fdd530.zip | |
RDMA/uverbs: Do not discard the IB_EVENT_DEVICE_FATAL event
The commit below moved all of the destruction to the disassociate step and
cleaned up the event channel during destroy_uobj.
However, when ib_uverbs_free_hw_resources() pushes IB_EVENT_DEVICE_FATAL
and then immediately goes to destroy all uobjects this causes
ib_uverbs_free_event_queue() to discard the queued event if userspace
hasn't already read() it.
Unlike all other event queues async FD needs to defer the
ib_uverbs_free_event_queue() until FD release. This still unregisters the
handler from the IB device during disassociation.
Fixes: 3e032c0e92aa ("RDMA/core: Make ib_uverbs_async_event_file into a uobject")
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Yishai Hadas <[email protected]>
Signed-off-by: Leon Romanovsky <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions