diff options
| author | Sean Hefty <[email protected]> | 2011-02-23 08:17:40 -0800 |
|---|---|---|
| committer | Roland Dreier <[email protected]> | 2011-03-15 10:56:12 -0700 |
| commit | 29963437a48475036353b95ab142bf199adb909e (patch) | |
| tree | 23564281f4d60b7a9cdbaab5e1babe3f67cc8ca8 /tools/perf/scripts/python | |
| parent | 25ae21a10112875763c18b385624df713a288a05 (diff) | |
IB/cm: Bump reference count on cm_id before invoking callback
When processing a SIDR REQ, the ib_cm allocates a new cm_id. The
refcount of the cm_id is initialized to 1. However, cm_process_work
will decrement the refcount after invoking all callbacks. The result
is that the cm_id will end up with refcount set to 0 by the end of the
sidr req handler.
If a user tries to destroy the cm_id, the destruction will proceed,
under the incorrect assumption that no other threads are referencing
the cm_id. This can lead to a crash when the cm callback thread tries
to access the cm_id.
This problem was noticed as part of a larger investigation with kernel
crashes in the rdma_cm when running on a real time OS.
Signed-off-by: Sean Hefty <[email protected]>
Acked-by: Doug Ledford <[email protected]>
Cc: <[email protected]>
Signed-off-by: Roland Dreier <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions