aboutsummaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorSean Hefty <sean.hefty@intel.com>2011-02-23 08:17:40 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2011-03-23 13:03:37 -0700
commit6fee8c663b4c7253b4ee68ae2680c8c4cb25a986 (patch)
tree99c3667cbdc8f8f246bb04c1f189065dd2d72f6a /arch
parentcd970182abeff0e63d85674d090fb59855b89124 (diff)
downloadlinux-2.6.38-lt-ux500-6fee8c663b4c7253b4ee68ae2680c8c4cb25a986.tar.gz
IB/cm: Bump reference count on cm_id before invoking callback
commit 29963437a48475036353b95ab142bf199adb909e upstream. 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> Signed-off-by: Roland Dreier <roland@purestorage.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions