We saw deadlock in mlx5_destroy_qp() if ibv_start_poll() returns EBUSY failure.
According to reference (https://man7.org/linux/man-pages/man3/ibv_create_cq_ex.3.html), if ibv_start_poll() returns error, ibv_end_poll() shouldn't be called.
Therefore, we must release the CQ lock in mlx5_start_poll() if mlx5dv_get_clock_info() returns error e.g. EBUSY.
The comparison function dev_cmp() doesn't work with 64b pointers in some
cases, as it casts the pointer to int. For example it's not able to sort
this list:
{0xfffe0c2f0b00, 0xaaac741b4a90, 0xaaac741b4d70}
Fixes: e5d371cb0af0 ("librdmacm: Globally store and sort IB device list")
Signed-off-by: Mark Zhang <email address hidden>
Reviewed-by: Leon Romanovsky <email address hidden>
Signed-off-by: Yishai Hadas <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
When the server accepts a UD connection request in sync mode,
the event needs to be acked, otherwise destroying the
listening id would get stuck because there is a pending event.
For RC, the event is acked in ucma_complete().
Fixes: 332b203d1a30 ("librdmacm: Do not wait in rdma_accept for UD QPs")
Signed-off-by: Oren Sidi <email address hidden>
Reviewed-by: Leon Romanovsky <email address hidden>
Reviewed-by: Sean Hefty <email address hidden>
Signed-off-by: Yishai Hadas <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
Fix the error flow of qelr_alloc_context() by making sure to free the
allocated resources.
Fixes: cae4a99ae679 ("libqedr: add support for XRC-SRQ's.")
Signed-off-by: Kamal Heib <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
0ceabd5...
by
Nicolas Morey <email address hidden>
Bump to version 32.12
Signed-off-by: Nicolas Morey <email address hidden>
6835f90...
by
Yevgeny Kliteynik <email address hidden>
mlx5: DR, Use the right GVMI number for drop action
When FW provides ICM addresses for drop RX/TX, the provided capability
is 64 bits that contain its GVMI as well as the ICM address itself. In
case of TX DROP this GVMI is different from the GVMI that the domain is
operating on.
This patch fixes the action to use this GVMI ID, as provided by FW.
