IB/mad: Fix race between cancel and receive completion

When ib_cancel_mad() is called, it puts the canceled send on a list
and schedules a "flushed" callback from process context. However,
this leaves a window where a receive completion could be processed
before the send is fully flushed.

This is fine, except that ib_find_send_mad() will find the MAD and
return it to the receive processing, which results in the sender
getting both a successful receive and a "flushed" send completion for
the same request. Understandably, this confuses the sender, which is
expecting only one of these two callbacks, and leads to grief such as
a use-after-free in IPoIB.

Fix this by changing ib_find_send_mad() to return a send struct only
if the status is still successful (and not "flushed"). The search of
the send_list already had this check, so this patch just adds the same
check to the search of the wait_list.

Signed-off-by: Roland Dreier <rolandd@cisco.com>

+1 -1
+1 -1
drivers/infiniband/core/mad.c
··· 1750 1750 */ 1751 1751 (is_direct(wc->recv_buf.mad->mad_hdr.mgmt_class) || 1752 1752 rcv_has_same_gid(mad_agent_priv, wr, wc))) 1753 - return wr; 1753 + return (wr->status == IB_WC_SUCCESS) ? wr : NULL; 1754 1754 } 1755 1755 1756 1756 /*