aboutsummaryrefslogtreecommitdiff
path: root/arch/x86
diff options
context:
space:
mode:
authorSean Hefty <sean.hefty@intel.com>2011-02-23 08:17:40 -0800
committerAK <andi@firstfloor.org>2011-03-31 11:58:38 -0700
commitca78068b35522c820207b36191cba1385163f198 (patch)
tree5c263f66c9eff5db1006785f3cda3ea1900b01fb /arch/x86
parentaf8c55e566b98985bde53ce09e72afcc6db04d4f (diff)
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> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Diffstat (limited to 'arch/x86')
0 files changed, 0 insertions, 0 deletions