diff options
author | Sean Hefty <sean.hefty@intel.com> | 2007-09-24 13:19:09 -0700 |
---|---|---|
committer | Roland Dreier <rolandd@cisco.com> | 2007-10-16 12:25:00 -0700 |
commit | c5483388bb4d771007ef36478db038e07922a020 (patch) | |
tree | c3e7304a88c0e856d28abaf3219a82e518ea6e9c /fs/jfs/file.c | |
parent | ab8403c424a35364a3a2c753f7c5917fcbb4d809 (diff) |
RDMA/cma: Add locking around QP accesses
If a user allocates a QP on an rdma_cm_id, the rdma_cm will automatically
transition the QP through its states (RTR, RTS, error, etc.) While the
QP state transitions are occurring, the QP itself must remain valid.
Provide locking around the QP pointer to prevent its destruction while
accessing the pointer.
This fixes an issue reported by Olaf Kirch from Oracle that resulted in
a system crash:
"An incoming connection arrives and we decide to tear down the nascent
connection. The remote ends decides to do the same. We start to shut
down the connection, and call rdma_destroy_qp on our cm_id. ... Now
apparently a 'connect reject' message comes in from the other host,
and cma_ib_handler() is called with an event of IB_CM_REJ_RECEIVED.
It calls cma_modify_qp_err, which for some odd reason tries to modify
the exact same QP we just destroyed."
Signed-off-by: Sean Hefty <sean.hefty@intel.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'fs/jfs/file.c')
0 files changed, 0 insertions, 0 deletions