Eli Cohen f868cae619 IB/mlx5: Fix post send fence logic ... commit c9b254955b9f8814966f5dabd34c39d0e0a2b437 upstream. If the caller specified IB_SEND_FENCE in the send flags of the work request and no previous work request stated that the successive one should be fenced, the work request would be executed without a fence. This could result in RDMA read or atomic operations failure due to a MR being invalidated. Fix this by adding the mlx5 enumeration for fencing RDMA/atomic operations and fix the logic to apply this. Fixes: e126ba97db ('mlx5: Add driver for Mellanox Connect-IB adapters') Signed-off-by: Eli Cohen <eli@mellanox.com> Signed-off-by: Leon Romanovsky <leon@kernel.org> Signed-off-by: Doug Ledford <dledford@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2016-08-20 18:09:25 +02:00
..
cmd.h
cq.h
device.h	IB/mlx5: Expose correct max_sge_rd limit	2016-05-04 14:48:48 -07:00
doorbell.h
driver.h	net/mlx5e: Device's mtu field is u16 and not int	2016-05-18 17:06:36 -07:00
flow_table.h
mlx5_ifc.h
qp.h	IB/mlx5: Fix post send fence logic	2016-08-20 18:09:25 +02:00
srq.h
vport.h