Bug Fixes in This Version

Linux Kernel Upstream Release Notes v5.17

Below are the bugs fixed in this version. For a list of fixes previous version, see Bug Fixes History.

Internal Reference Number

Description

3032335

Description: Creating multiple steering rules that modify a packet and match on the same packet headers can cause an error to be displayed in dmesg when deleting the steering rules.

Keywords: Steering Rules

Fixed in Release: 5.7-1.0.2.0

3011368

Description: Some IB spec QP state behaviour on post_send()/recv() is not being fully enforced. The fix makes the QP complaint to IB spec about when it is allowed to post_send()/recv() and when it should return an error.

Keywords: RDMA, IB spec QP

Fixed in Release: 5.7-1.0.2.0

3075125

Description: When changing trust state from PCP to DSCP, the TC number changes by default to 8, in some cases, disrupting traffic prioritization if trust state is changed back to PCP.

Keywords: NetDev, QoS

Discovered in Release: 5.4-1.0.3.0

Fixed in Release: 5.7-1.0.2.0

3054413

Description: In the current release, the following OPNs/PSIDs should be manually upgraded:

MCX753106AS-HEA-N NVD0000000023

MCX75310AAS-HEA-N NVD0000000024

Keywords: ConnectX-7, Upgrade

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

3070653

Description: In versions of MLNX_OFED before 5.7, the xpmem kernel module was not signed. When it was installed on systems (mostly RHEL and other compatible systems) the following error message would appear: "xpmem: loading out-of-tree module taints kernel."

Keywords: Installation, xpmem

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

3075357

Description: In Debian-based distributions, in /etc/init.d/openibd, the path to enable the firmware tracer is /sys/kernel/debug/tracing/events/mlx5/fw_tracer/enable instead of /sys/kernel/debug/tracing/events/mlx5/mlx5_fw/enable . As a result, firmware tracer will never get enabled even when supported.

Keywords: Installation, Kernel Trace Debug

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

2688191

Description: The minimum Tx rate limit is not supported with link speed of 1Gb/s.

Keywords: Rate Limit, 1Gb/s

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

3044255

Description: Destroying mlxdevm group while SF is attached to it is not supported.

Keywords: ASAP2, mlxdevm, QoS, Group, Scalable Functions

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

3047142

Description: Using OVS offload with NIC mode (non switchdev mode) causes traffic to drop.

Keywords: ASAP2, Offload, NIC Mode, OVS

Discovered in Release: 5.6-1.0.3.3

Fixed in Release: 5.7-1.0.2.0

3123986

Description: In some cases VF metering configuration failure caused a deadlock.

Keywords: ASAP2, VF Metering

Discovered in Release: 5.5-1.0.3.2

Fixed in Release: 5.7-1.0.2.0

3053842

Description: A race condition may cause some connection aging to set to 24 hours instead of 30 seconds.

Keywords: ASAP2, Connection Tracking, Aging

Discovered in Release: 5.5-1.0.3.2

Fixed in Release: 5.7-1.0.2.0

© Copyright 2023, NVIDIA. Last updated on Nov 27, 2023.