Focal: $ uname -r 5.4.0-97-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1 RTNETLINK answers: Operation not permitted $ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $? 0 Looks good - vlan 0 programming doesn't result in EPERM as expected contrary to non-zero vlans. Will try others as well. It would be good to backport it to currently released versions above Focal (for production, we are mostly looking for Focal GA + HWE kernels but it keeping it fixed consistently seems like the right approach). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: New Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
