diff options
| author | Jack Morgenstein <[email protected]> | 2025-05-21 11:36:02 +0000 |
|---|---|---|
| committer | Jason Gunthorpe <[email protected]> | 2025-05-26 18:36:46 +0000 |
| commit | 92a251c3df8ea1991cd9fe00f1ab0cfce18d7711 (patch) | |
| tree | f8c63aeabffa72189af9ef5d0ddd1678d1e584a2 /scripts/gcc-plugins/sancov_plugin.c | |
| parent | Merge tag 'v6.15' into rdma.git for-next (diff) | |
| download | kernel-92a251c3df8ea1991cd9fe00f1ab0cfce18d7711.tar.gz kernel-92a251c3df8ea1991cd9fe00f1ab0cfce18d7711.zip | |
RDMA/cma: Fix hang when cma_netevent_callback fails to queue_work
The cited commit fixed a crash when cma_netevent_callback was called for
a cma_id while work on that id from a previous call had not yet started.
The work item was re-initialized in the second call, which corrupted the
work item currently in the work queue.
However, it left a problem when queue_work fails (because the item is
still pending in the work queue from a previous call). In this case,
cma_id_put (which is called in the work handler) is therefore not
called. This results in a userspace process hang (zombie process).
Fix this by calling cma_id_put() if queue_work fails.
Fixes: 45f5dcdd0497 ("RDMA/cma: Fix workqueue crash in cma_netevent_work_handler")
Link: https://patch.msgid.link/r/4f3640b501e48d0166f312a64fdadf72b059bd04.1747827103.git.leon@kernel.org
Signed-off-by: Jack Morgenstein <[email protected]>
Signed-off-by: Feng Liu <[email protected]>
Reviewed-by: Vlad Dumitrescu <[email protected]>
Signed-off-by: Leon Romanovsky <[email protected]>
Reviewed-by: Sharath Srinivasan <[email protected]>
Reviewed-by: Kalesh AP <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/sancov_plugin.c')
0 files changed, 0 insertions, 0 deletions
