IB/cm: Bump reference count on cm_id before invoking callback
authorSean Hefty <sean.hefty@intel.com>
Wed, 23 Feb 2011 16:17:40 +0000 (08:17 -0800)
committerRoland Dreier <roland@purestorage.com>
Tue, 15 Mar 2011 17:56:12 +0000 (10:56 -0700)
commit29963437a48475036353b95ab142bf199adb909e
tree23564281f4d60b7a9cdbaab5e1babe3f67cc8ca8
parent25ae21a10112875763c18b385624df713a288a05
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 <sean.hefty@intel.com>
Acked-by: Doug Ledford <dledford@redhat.com>
Cc: <stable@kernel.org>
Signed-off-by: Roland Dreier <roland@purestorage.com>
drivers/infiniband/core/cm.c
This page took 0.045173 seconds and 5 git commands to generate.