Maxim Mikityanskiy 36d45fb9d2 net/mlx5e: Fix repeated XSK usage on one channel ... After an XSK is closed, the relevant structures in the channel are not zeroed. If an XSK is opened the second time on the same channel without recreating channels, the stray values in the structures will lead to incorrect operation of queues, which causes CQE errors, and the new socket doesn't work at all. This patch fixes the issue by explicitly zeroing XSK-related structs in the channel on XSK close. Note that those structs are zeroed on channel creation, and usually a configuration change (XDP program is set) happens on XSK open, which leads to recreating channels, so typical XSK usecases don't suffer from this issue. However, if XSKs are opened and closed on the same channel without removing the XDP program, this bug reproduces. Fixes: db05815b36 ("net/mlx5e: Add XSK zero-copy support") Signed-off-by: Maxim Mikityanskiy <maximmi@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>		2020-06-11 15:37:55 -07:00
..
mlx4	RDMA 5.8 merge window pull request	2020-06-05 14:05:57 -07:00
mlx5/core	net/mlx5e: Fix repeated XSK usage on one channel	2020-06-11 15:37:55 -07:00
mlxfw	net/mlxfw: Remove unneeded semicolon	2020-04-24 16:56:22 -07:00
mlxsw	mlxsw: core: Use different get_trend() callbacks for different thermal zones	2020-06-07 16:59:43 -07:00
Kconfig	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00