[Bug 2060969] Re: UB 24.04: update uproute2 package
** Description changed: This ticket is an FR to update iproute2 package from 6.1.0 to latest upstream version. This updated is needed to support latest mlx5 driver features. - Missing support examples (iproute v6.7): - 1) - ipsec + Missing support examples + 1) related feature: ipsec packet offload (iproute v6.7): https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/ 994e80e9 devlink: Support setting port function ipsec_packet cap 27fd1bfa devlink: Support setting port function ipsec_crypto cap kernel https://www.spinics.net/lists/netdev/msg932050.html - 2) + 2) related feature: live migration (iproute2 v6.2.0) + https://lore.kernel.org/netdev/2022125849.510284-5-sh...@nvidia.com/T/ + e036c36 devlink: Add documentation for roce and migratable port function attributes + 32168d8a devlink: Support setting port function migratable cap + bb2eea91 devlink: Support setting port function roce cap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060969 Title: UB 24.04: update uproute2 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060969] [NEW] UB 24.04: update uproute2 package
Public bug reported: This ticket is an FR to update iproute2 package from 6.1.0 to latest upstream version. This updated is needed to support latest mlx5 driver features. Missing support examples (iproute v6.7): 1) ipsec https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/ 994e80e9 devlink: Support setting port function ipsec_packet cap 27fd1bfa devlink: Support setting port function ipsec_crypto cap kernel https://www.spinics.net/lists/netdev/msg932050.html 2) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: This ticket is an FR to update iproute2 package from 6.1.0 to latest upstream version. This updated is needed to support latest mlx5 driver features. - Missing support examples: - 1) - ipsec + Missing support examples (iproute v6.7): + 1) + ipsec https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/ 994e80e9 devlink: Support setting port function ipsec_packet cap 27fd1bfa devlink: Support setting port function ipsec_crypto cap kernel https://www.spinics.net/lists/netdev/msg932050.html 2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060969 Title: UB 24.04: update uproute2 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Hi, We tested the feature with 5.15.0-28 from proposed. The features is working and SMFS mode is enabled for Connectx-7. No degradation detected comparing 5.15.0-28 from proposed and 5.15.0-28 compiled without the feature patch set. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Hi Dan, Those test are ASAP which uses steering as its infrastructure thus this test set when configured to run with software steering verifies the functionality. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
I applied same test plan on 5.15.0-25-generic with and without the feature patchset on CX6-dx. In both cases the test kernel had the the problematic patch from (bug https://bugs.launchpad.net/bugs/1967754) reverted. I got the exact same results as in comment #6 so the patch set does not introduce a degradation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Hi, I run some tests to verify the feature. SMFS was enabled on CX7 setup # devlink dev param show pci/:08:00.0 name flow_steering_mode pci/:08:00.0: name flow_steering_mode type driver-specific values: cmode runtime value smfs but some of the asap test failed (see below), it will be great to have a test kernel without the feature and without the degradation from bug 1967754 to make sure those failure are not caused by this ticket patch set (testing with Cx6-dx). test-ct-tcp.sh TEST PASSED test-eswitch-add-in-mode1-del-in-mode2.shTEST PASSED test-eswitch-netdev-tx.shTEST PASSED test-eswitch-reload-modules-different-state.sh FAILED test-eswitch-set-vf-vlan.sh TEST PASSED test-mod-depends.sh TEST PASSED test-ovs-ct-scapy-udp-nat-dnat.shTEST PASSED test-ovs-ct-vxlan.sh FAILED test-ovs-sf-tcp.sh TEST PASSED test-tc-groups-multi-fgs.sh TEST PASSED test-tc-groups-overlapping.shTEST PASSED test-tc-hairpin-rules.sh TEST PASSED test-tc-icmp-4-channels.sh TEST PASSED test-tc-insert-rules.sh FAILED test-tc-insert-rules-geneve.sh TEST PASSED test-tc-insert-rules-goto.sh TEST PASSED test-tc-insert-rules-goto2.shTEST PASSED test-tc-insert-rules-mirror.sh TEST PASSED test-tc-insert-rules-pedit.shTEST PASSED test-tc-merged-esw-vf-vf.sh TEST PASSED test-tc-vf-mirror.sh TEST PASSED test-tc-vxlan-decap-inner-match-drop.sh TEST PASSED test-vf-lag.sh TEST PASSED test-vf-vf-ping.sh TEST PASSED test-vxlan-neigh-update.sh FAILED -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
with cf530217408e ("devlink: Notify users when objects are accessible")
i was able to change steering mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
https://lore.kernel.org/netdev/cover.1632565508.git.leo...@nvidia.com/
It seems jammy kernel needs cf530217408e ("devlink: Notify users when objects
are accessible") from v5.16-rc1
(see link) the old devlink_register (before cf530217408e) implementation do
not publish the params so we cannot erase the calls to devlink_params_publish.
i'll update once finished testing with cf530217408e ported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
** Description changed:
-
- on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode
+ on kernel 5.15.0-23-generic devlink cannot show/change flow steering
+ mode
[test case]
# devlink dev param show pci/:24:00.0 name flow_steering_mode
pci/:24:00.0:
- name flow_steering_mode type driver-specific
- values:
-
- (flow steering mode description is missing beneath values)
+ name flow_steering_mode type driver-specific
+ values:
+ (flow steering mode description is missing beneath "values:")
# devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs
cmode runtime
Segmentation fault (core dumped)
and also with upstream iproute
# ./iproute2/devlink/devlink dev param set pci/:24:00.0 name
flow_steering_mode value smfs cmode runtime
Configuration mode not supported
this issue is a degradation introduced by commit from jammy tree
76385c47db37 ("net/mlx5: Accept devlink user input after driver
initialization complete")
issue do not repro on v5.15.0 or when the above commit is reverted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] [NEW] ubuntu 22.04 jammy, mlx5, can't change flow steering mode
Public bug reported:
on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode
[test case]
# devlink dev param show pci/:24:00.0 name flow_steering_mode
pci/:24:00.0:
name flow_steering_mode type driver-specific
values:
(flow steering mode description is missing beneath values)
# devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs
cmode runtime
Segmentation fault (core dumped)
and also with upstream iproute
# ./iproute2/devlink/devlink dev param set pci/:24:00.0 name
flow_steering_mode value smfs cmode runtime
Configuration mode not supported
this issue is a degradation introduced by commit from jammy tree
76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization
complete")
issue do not repro on v5.15.0 or when the above commit is reverted.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Hi Dan, 98576013bf283 net/mlx5: DR, Add missing string for action type SAMPLER was omitted by mistake, sorry for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy
reply to comment #4 on cx7 setup with 5.15.0-23-generic and Ib_virt capability set to 0 we see the correct speed is exposed by ibv_devinfo so the feature works as expected # ibv_devinfo -v|grep active_speed active_speed: 100.0 Gbps (128) active_speed: 100.0 Gbps (128) active_speed: 100.0 Gbps (128) active_speed: 100.0 Gbps (128) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] [NEW] [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Public bug reported: [Impact] Add support for software steering on cx7 [Test Case] configure software steering on cx7 setup run asap testing (reference https://github.com/Mellanox/ovs-tests) [Regression Potential] TBD [Other Info] Feature patchset: All patches are cleanly applied on Jamy master-next beside these two who add minor conflicts due to context difference. net/mlx5: Introduce software defined steering capabilities net/mlx5: DR, Add support for matching on #fixes 624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF 0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #CX7 SMFS support 6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering 638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1 75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in HW spec bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE in STEv1 11659ef8d28e net/mlx5: DR, Remove unneeded comments 5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length (IHL) #dependencies: 60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX 8348b71ccd92 net/mlx5: Introduce software defined steering capabilities #depencecies: #SW STEERING DEBUG DUMP aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports it 4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers f59464e257bd net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field 09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1 8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs 0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type 9222f0b27da2 net/mlx5: DR, Add support for dumping steering info 7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param 89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value 08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node 32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_" 84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher 58a606dba708 net/mlx5: Introduce new uplink destination type 455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #SW STEERING SF 515ce2ffa621 net/mlx5: DR, init_next_match only if needed 5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset' 1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32 11a45def2e19 net/mlx5: DR, Add support for SF vports c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport caps dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0 7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing MLX5_VPORT_UPLINK f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16 c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963926] Re: focal , mlx5, steering, Add support for non FDB domain
** Description changed: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] - install latest DPDK from github + install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd - $ mason build + $ mason build $ ninja -C build - - - Run testpmd + - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask- event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " - testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end + testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end - port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported - + port_flow_complain(): Caught PMD error type 16 (specific action): cannot + create jump action.: Operation not supported + testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec + 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask + FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan + has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask + 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / + end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr + 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / + raw_decap index 0 / raw_encap index 0 / count / end - testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end - - port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument - + port_flow_complain(): Caught PMD error type 16 (specific action): can't + create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory - - - testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory - [Regression Potential] - TBD + regression potential is low since we are adding a new capability to support rx/tx domains without touching/changing behaviour of any existing functionality. [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963926] Re: focal , mlx5, steering, Add support for non FDB domain
** Summary changed: - mlx5: steering, Add support for non FDB domain + focal ,mlx5, steering, Add support for non FDB domain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963926] [NEW] mlx5: steering, Add support for non FDB domain
Public bug reported: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask- event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963926 Title: mlx5: steering, Add support for non FDB domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962185] [NEW] Add ConnectX7 support and bug fixes to Jammy
Public bug reported: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
** Description changed: [impact] Add Support for flow counters offset for bulk counters on kernel side. Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on user space side only with these 3 rdma-core patches from v27.0 3956cf74 mlx5: Add support for bulk flow counters steering actions 65ed59c6 Update kernel headers b32eee70 mlx5: Fix typos [test case] /* download and install dpdk from github (issue do not reproduce with inbox dpdk) */ $ git clone https://github.com/mellanox/dpdk.org $ cd dpdk.org/ /* install dependencies if needed */ $ apt-get install -y python3-pyelftools python-pyelftools $ apt install meson $ meson build-meson $ ninja -C build-meson/ /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0, :05:00.1 are pci id for the cx5 devices */ //dpdk.org/build-meson/app/dpdk-testpmd -v -n 4 -w :05:00.0,txq_inline=147,rx_vec_en=1 -w :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i --nb- cores=7 --txd=8192 --rxd=8192 --burst=64 EAL: Detected 12 lcore(s) EAL: Detected 2 NUMA nodes EAL: RTE Version: 'DPDK 21.05.0-rc0' Option -w, --pci-whitelist is deprecated, use -a, --allow option instead Option -w, --pci-whitelist is deprecated, use -a, --allow option instead EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0) mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: Default miss action is not supported. mlx5_pci: Unexpected error in counter offset support detection /* LINE INDICATING ERROR*/ EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.1 (socket 0) mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: Default miss action is not supported. mlx5_pci: Unexpected error in counter offset support detection /* LINE INDICATING ERROR*/ Interactive-mode selected testpmd: create a new mbuf pool : n=327680, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc testpmd: create a new mbuf pool : n=327680, size=2176, socket=1 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) Port 0: 0C:42:A1:D1:D0:64 Configuring Port 1 (socket 0) Port 1: 0C:42:A1:D1:D0:65 Checking link statuses... Done testpmd> two lines indicates errors in counter offset supports detection. [Fix] the issue is fixed with the following upstream commit from v5.5-rc1 which cleanly applied above focal. 208d70f562e5 IB/mlx5: Support flow counters offset for bulk counters Our QA-dpdk team tested the focal kernel with this patch and found no issues. + [regression potential] + function mlx5_ib devx _is_flow_counter (from the devx interface) signature has changed so anything that uses it like rdma-core might be impacted. + Thanks, Amir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922494 Title: Ubuntu 20.04 - 'Support flow counters offset for bulk counters' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
Hi Tim, It extends devx interface and might affects any user space application that uses rdma-core (which already has relevant patches), dpdk for instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922494 Title: Ubuntu 20.04 - 'Support flow counters offset for bulk counters' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922494] [NEW] Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
Public bug reported: [impact] Add Support for flow counters offset for bulk counters on kernel side. Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on user space side only with these 3 rdma-core patches from v27.0 3956cf74 mlx5: Add support for bulk flow counters steering actions 65ed59c6 Update kernel headers b32eee70 mlx5: Fix typos [test case] /* download and install dpdk from github (issue do not reproduce with inbox dpdk) */ $ git clone https://github.com/mellanox/dpdk.org $ cd dpdk.org/ /* install dependencies if needed */ $ apt-get install -y python3-pyelftools python-pyelftools $ apt install meson $ meson build-meson $ ninja -C build-meson/ /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0, :05:00.1 are pci id for the cx5 devices */ //dpdk.org/build-meson/app/dpdk-testpmd -v -n 4 -w :05:00.0,txq_inline=147,rx_vec_en=1 -w :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i --nb- cores=7 --txd=8192 --rxd=8192 --burst=64 EAL: Detected 12 lcore(s) EAL: Detected 2 NUMA nodes EAL: RTE Version: 'DPDK 21.05.0-rc0' Option -w, --pci-whitelist is deprecated, use -a, --allow option instead Option -w, --pci-whitelist is deprecated, use -a, --allow option instead EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0) mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: Default miss action is not supported. mlx5_pci: Unexpected error in counter offset support detection /* LINE INDICATING ERROR*/ EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.1 (socket 0) mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: Default miss action is not supported. mlx5_pci: Unexpected error in counter offset support detection /* LINE INDICATING ERROR*/ Interactive-mode selected testpmd: create a new mbuf pool : n=327680, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc testpmd: create a new mbuf pool : n=327680, size=2176, socket=1 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) Port 0: 0C:42:A1:D1:D0:64 Configuring Port 1 (socket 0) Port 1: 0C:42:A1:D1:D0:65 Checking link statuses... Done testpmd> two lines indicates errors in counter offset supports detection. [Fix] the issue is fixed with the following upstream commit from v5.5-rc1 which cleanly applied above focal. 208d70f562e5 IB/mlx5: Support flow counters offset for bulk counters Our QA-dpdk team tested the focal kernel with this patch and found no issues. Thanks, Amir ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - [impact] Add Support for flow counters offset for bulk counters on kernel side. - Currently Ubuntu 20.04 has 'flow counters offset for bulk counters' on user space side only with these 3 rdma-core patches from v27.0 + Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on user space side only with these 3 rdma-core patches from v27.0 3956cf74 mlx5: Add support for bulk flow counters steering actions 65ed59c6 Update kernel headers b32eee70 mlx5: Fix typos - [test case] - /* download and install dpdk from github (issue do not reproduce with inbox dpdk) */ + /* download and install dpdk from github (issue do not reproduce with inbox dpdk) */ $ git clone https://github.com/mellanox/dpdk.org $ cd dpdk.org/ /* install dependencies if needed */ $ apt-get install -y python3-pyelftools python-pyelftools $ apt install meson $ meson build-meson $ ninja -C build-meson/ /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0, :05:00.1 are pci id for the cx5 devices */ //dpdk.org/build-meson/app/dpdk-testpmd -v -n 4 -w :05:00.0,txq_inline=147,rx_vec_en=1 -w :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i --nb- cores=7 --txd=8192 --rxd=8192 --burst=64 EAL: Detected 12 lcore(s) EAL: Detected 2 NUMA nodes EAL: RTE Version: 'DPDK 21.05.0-rc0' Option -w, --pci-whitelist is deprecated, use -a, --allow option instead Option -w, --pci-whitelist is deprecated, use -a, --allow option instead EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0) mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max mlx5_pci: Default miss action is not
[Bug 1922472] Re: Ubuntu 20.04, mlx5 driver - CQE with err creating geneve tunnel in a VF
** Description changed: [Impact] On mlx5 device, When creating geneve tunnel in a Virtual Function and setting it up error are logged in kernel buffer. [test case] using two setups connected back to back on both sides create vf's $ echo 1 > /sys/class/net/ens5f0/device/sriov_numvfs add ip-es to vf's interfaces on both sides (13.194.5.1/16, 13.194.6.1/16) $ ip a add 13.194.5.1/16 dev ens5f0v0 set interfaces on both sides up $ ip l set dev ens5f0v0 up check connectivity $ ping 13.194.6.1 -I 13.194.5.1 -c 6 - on both sides define geneve tunnel with id 300 over the vf-s - $ ip link add name gen_vf type geneve id 300 remote 13.194.6.1 + on both sides define geneve tunnel with same id over the vf-s + $ ip link add name gen_vf type geneve id 300 remote 13.194.6.1 add ip addresses to geneve interfaces on both sides (14.194.5.1/16, 14.194.6.1/16) - $ ip a add 14.194.5.1/16 dev gen_vf + $ ip a add 14.194.5.1/16 dev gen_vf set geneve interfaces up $ ip l set dev gen_vf up check log - $ dmesg - [ 1221.501048] mlx5_core :24:00.2 ens5f0v0: Error cqe on cqn 0x48a, ci 0x9, sqn 0x116, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 + $ dmesg + [ 1221.501048] mlx5_core :24:00.2 ens5f0v0: Error cqe on cqn 0x48a, ci 0x9, sqn 0x116, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 1221.501179] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501183] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501185] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501188] 0030: 00 00 00 00 6a 10 68 02 0a 00 01 16 00 09 20 d2 [ 1221.501240] mlx5_core :24:00.2 ens5f0v0: ERR CQE on SQ: 0x116 [ 1222.930608] mlx5_core :24:00.2 ens5f0v0: Error cqe on cqn 0x48e, ci 0x5, sqn 0x11b, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 1222.930733] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930736] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930739] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930741] 0030: 00 00 00 00 6a 10 68 02 0a 00 01 1b 00 05 2d d2 [ 1222.930791] mlx5_core :24:00.2 ens5f0v0: ERR CQE on SQ: 0x11b [Fix] - The issue was solved upstream v5.12-rc1 with + The issue was solved upstream v5.12-rc1 with e1c3940c6003 net/mlx5e: Check tunnel offload is required before setting SWP The attached patch is modification of e1c3940c6003 for focal kernel. [Regression Potential] - Regression risk is low as It is a very small fix which was also tested thoroughly on upstream + Regression risk is low as It is a very small fix which was also tested thoroughly on upstream setups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922472 Title: Ubuntu 20.04, mlx5 driver - CQE with err creating geneve tunnel in a VF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922472] [NEW] Ubuntu 20.04, mlx5 driver - CQE with err creating geneve tunnel in a VF
Public bug reported: [Impact] On mlx5 device, When creating geneve tunnel in a Virtual Function and setting it up error are logged in kernel buffer. [test case] using two setups connected back to back on both sides create vf's $ echo 1 > /sys/class/net/ens5f0/device/sriov_numvfs add ip-es to vf's interfaces on both sides (13.194.5.1/16, 13.194.6.1/16) $ ip a add 13.194.5.1/16 dev ens5f0v0 set interfaces on both sides up $ ip l set dev ens5f0v0 up check connectivity $ ping 13.194.6.1 -I 13.194.5.1 -c 6 on both sides define geneve tunnel with id 300 over the vf-s $ ip link add name gen_vf type geneve id 300 remote 13.194.6.1 add ip addresses to geneve interfaces on both sides (14.194.5.1/16, 14.194.6.1/16) $ ip a add 14.194.5.1/16 dev gen_vf set geneve interfaces up $ ip l set dev gen_vf up check log $ dmesg [ 1221.501048] mlx5_core :24:00.2 ens5f0v0: Error cqe on cqn 0x48a, ci 0x9, sqn 0x116, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 1221.501179] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501183] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501185] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1221.501188] 0030: 00 00 00 00 6a 10 68 02 0a 00 01 16 00 09 20 d2 [ 1221.501240] mlx5_core :24:00.2 ens5f0v0: ERR CQE on SQ: 0x116 [ 1222.930608] mlx5_core :24:00.2 ens5f0v0: Error cqe on cqn 0x48e, ci 0x5, sqn 0x11b, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 1222.930733] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930736] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930739] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 1222.930741] 0030: 00 00 00 00 6a 10 68 02 0a 00 01 1b 00 05 2d d2 [ 1222.930791] mlx5_core :24:00.2 ens5f0v0: ERR CQE on SQ: 0x11b [Fix] The issue was solved upstream v5.12-rc1 with e1c3940c6003 net/mlx5e: Check tunnel offload is required before setting SWP The attached patch is modification of e1c3940c6003 for focal kernel. [Regression Potential] Regression risk is low as It is a very small fix which was also tested thoroughly on upstream setups. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal ** Attachment added: "1-ubuntu20.04-net-mlx5e-Check-tunnel-offload-is-required-before-se.patch" https://bugs.launchpad.net/bugs/1922472/+attachment/5483885/+files/1-ubuntu20.04-net-mlx5e-Check-tunnel-offload-is-required-before-se.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922472 Title: Ubuntu 20.04, mlx5 driver - CQE with err creating geneve tunnel in a VF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
I reviewed the groovy patch and It looks fine! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915717] Re: Ubuntu 21.04, kernel feature request, TLS device offload for Bond
The test kernel was verified successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915717 Title: Ubuntu 21.04, kernel feature request, TLS device offload for Bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915717] Re: Ubuntu 21.04, kernel feature request, TLS device offload for Bond
Hi, I retried and All 8 commits were cleanly applied above tag: Ubuntu-unstable-5.11.0-10.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915717 Title: Ubuntu 21.04, kernel feature request, TLS device offload for Bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915717] [NEW] Ubuntu 21.04, kernel feature request, TLS device offload for Bond
Public bug reported: The request here is to pull needed patches to support tls rx/tx offload for bond interfaces. patch set: 4e5a73329051 net/tls: Except bond interface from some TLS checks 153cbd137f0a net/tls: Device offload to use lowest netdevice in chain dc5809f9e2b6 net/bonding: Declare TLS RX device offload support 89df6a810470 net/bonding: Implement TLS TX device offload f45583de361d net/bonding: Take update_features call out of XFRM funciton 007feb87fb15 net/bonding: Implement ndo_sk_get_lower_dev 5b99854540e3 net/bonding: Take IP hash logic into a helper 719a402cf603 net: netdevice: Add operation ndo_sk_get_lower_dev https://www.spinics.net/lists/netdev/msg714607.html https://www.spinics.net/lists/netdev/msg714991.html * the set was originally applied to net/net-next (hashes above are from net-next tree cloned from git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git) * The set is cleanly applied on ubuntu-unstable branch (cloned from git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable) * the set is accepted to upstream v5.12 and thus not natively in 21.04 thanks, Amir ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915717 Title: Ubuntu 21.04, kernel feature request, TLS device offload for Bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915403] Re: devlink: don't do reporter recovery if the state is healthy
** Description changed: Hi, [Impact] Currently in focal, devices reporter recovery is enabled even if state is healthy. [test case] 1) display devlink health status # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 0 grace_period 120 auto_recover true 2) perform reporter recovery using devlink, # devlink health recover pci/:05:00.0 reporter fw_fatal 3)see that recovery was performed. # dmesg [776733.438708] mlx5_core :05:00.0: mlx5_health_try_recover:316:(pid 563178): handling bad device here [776733.438717] mlx5_core :05:00.0: mlx5_handle_bad_state:278:(pid 563178): Expected to see disabled NIC but it is full driver [776735.591522] mlx5_core :05:00.0: mlx5_health_try_recover:328:(pid 563178): starting health recovery flow ... # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 1 grace_period 120 auto_recover true [fix] 402818205c9e devlink: don't do reporter recovery if the state is healthy this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal tree. the commit prevents reporter recovery when device in healthy state. when applied, issuing # devlink health recover pci/:05:00.0 reporter fw_fatal on healthy state reporter return successfully, but dmesg is clean and recover counter do not change. [Regression Potential] - very small as it is a very minor change. + very small as it is a very minor change, also this patch has been tested internally on upstream setups for a while and no degradation has been found. + one obvious change is that a user cannot force devlink recovery when state is healthy but I'm not aware of such use case. Thanks, Amir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915403 Title: devlink: don't do reporter recovery if the state is healthy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915403] Re: devlink: don't do reporter recovery if the state is healthy
I tested the kernel It works as expected and meets our needs thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915403 Title: devlink: don't do reporter recovery if the state is healthy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915403] Re: devlink: don't do reporter recovery if the state is healthy
** Description changed: Hi, [Impact] - Currently in focal, mlx5 devices reporter recovery is enabled even if state is healthy. + Currently in focal, devices reporter recovery is enabled even if state is healthy. [test case] 1) display devlink health status # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 0 grace_period 120 auto_recover true 2) perform reporter recovery using devlink, # devlink health recover pci/:05:00.0 reporter fw_fatal 3)see that recovery was performed. # dmesg [776733.438708] mlx5_core :05:00.0: mlx5_health_try_recover:316:(pid 563178): handling bad device here [776733.438717] mlx5_core :05:00.0: mlx5_handle_bad_state:278:(pid 563178): Expected to see disabled NIC but it is full driver [776735.591522] mlx5_core :05:00.0: mlx5_health_try_recover:328:(pid 563178): starting health recovery flow ... # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 1 grace_period 120 auto_recover true [fix] 402818205c9e devlink: don't do reporter recovery if the state is healthy this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal tree. the commit prevents reporter recovery when device in healthy state. when applied, issuing # devlink health recover pci/:05:00.0 reporter fw_fatal on healthy state reporter return successfully, but dmesg is clean and recover counter do not change. [Regression Potential] very small as it is a very minor change. Thanks, Amir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915403 Title: devlink: don't do reporter recovery if the state is healthy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915403] [NEW] devlink: don't do reporter recovery if the state is healthy
Public bug reported: Hi, [Impact] Currently in focal, mlx5 devices reporter recovery is enabled even if state is healthy. [test case] 1) display devlink health status # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 0 grace_period 120 auto_recover true 2) perform reporter recovery using devlink, # devlink health recover pci/:05:00.0 reporter fw_fatal 3)see that recovery was performed. # dmesg [776733.438708] mlx5_core :05:00.0: mlx5_health_try_recover:316:(pid 563178): handling bad device here [776733.438717] mlx5_core :05:00.0: mlx5_handle_bad_state:278:(pid 563178): Expected to see disabled NIC but it is full driver [776735.591522] mlx5_core :05:00.0: mlx5_health_try_recover:328:(pid 563178): starting health recovery flow ... # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: reporter fw_fatal state healthy error 0 recover 1 grace_period 120 auto_recover true [fix] 402818205c9e devlink: don't do reporter recovery if the state is healthy this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal tree. the commit prevents reporter recovery when device in healthy state. when applied, issuing # devlink health recover pci/:05:00.0 reporter fw_fatal on healthy state reporter return successfully, but dmesg is clean and recover counter do not change. [Regression Potential] very small as it is a very minor change. Thanks, Amir ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, [Impact] Currently in focal, mlx5 devices reporter recovery is enabled even if state is healthy. [test case] 1) display devlink health status # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: - reporter fw_fatal - state healthy error 0 recover 0 grace_period 120 auto_recover true + reporter fw_fatal + state healthy error 0 recover 0 grace_period 120 auto_recover true 2) perform reporter recovery using devlink, # devlink health recover pci/:05:00.0 reporter fw_fatal 3)see that recovery was performed. # dmesg [776733.438708] mlx5_core :05:00.0: mlx5_health_try_recover:316:(pid 563178): handling bad device here [776733.438717] mlx5_core :05:00.0: mlx5_handle_bad_state:278:(pid 563178): Expected to see disabled - NIC but it is full driver + NIC but it is full driver [776735.591522] mlx5_core :05:00.0: mlx5_health_try_recover:328:(pid 563178): starting health recovery flow ... # devlink health show pci/:05:00.0 reporter fw_fatal pci/:05:00.0: - reporter fw_fatal - state healthy error 0 recover 1 grace_period 120 auto_recover true + reporter fw_fatal + state healthy error 0 recover 1 grace_period 120 auto_recover true [fix] 402818205c9e devlink: don't do reporter recovery if the state is healthy this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal tree. the commit prevents reporter recovery when device in healthy state. - when applied, issuing - # devlink health recover pci/:05:00.0 reporter fw_fatal - on healthy state reporter return successfully, but dmesg is clean and recover counter do not change. + when applied, issuing + # devlink health recover pci/:05:00.0 reporter fw_fatal + on healthy state reporter return successfully, but dmesg is clean and recover counter do not change. + + [Regression Potential] + very small as it is a very minor change. Thanks, Amir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915403 Title: devlink: don't do reporter recovery if the state is healthy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
Hi Jeff, upstream commit 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler was picked to Ubuntu-5.4.0-56.62 kernel (hash bcd6e98bef76cc8a49a1b736b0fefffbffb75c30) (v5.4.71 upstream stable release, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902110 ) now a new issue arise reloading mlx5 modules causes an error message in kernel buffer "cmd_work_handler:887:(pid 292): failed to allocate command entry" reproduction: # modprobe -r mlx5_ib mlx5_core # modprobe mlx5_core mlx5_ib # dmesg [ 142.638490] mlx5_core :08:00.1: E-Switch: cleanup [ 143.734339] mlx5_core :08:00.0: E-Switch: cleanup [ 164.171511] mlx5_core: unknown parameter 'mlx5_ib' ignored [ 164.173501] mlx5_core :08:00.0: firmware version: 16.28.1002 [ 164.173576] mlx5_core :08:00.0: 126.016 Gb/s available PCIe bandwidth (8 GT/s x16 link) [ 164.457342] mlx5_core :08:00.0: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps [ 164.457365] mlx5_core :08:00.0: E-Switch: Total vports 2, per vport: max uc(1024) max mc(16384) [ 164.484659] port_module: 5 callbacks suppressed [ 164.484665] mlx5_core :08:00.0: Port module event: module 0, Cable plugged [ 164.485112] mlx5_core :08:00.0: mlx5_pcie_event:294:(pid 8): PCIe slot advertised sufficient power (75W). [ 164.494771] mlx5_core :08:00.1: firmware version: 16.28.1002 [ 164.494844] mlx5_core :08:00.1: 126.016 Gb/s available PCIe bandwidth (8 GT/s x16 link) [ 164.779534] mlx5_core :08:00.1: Rate limit: 127 rates are supported, range: 0Mbps to 97656Mbps [ 164.779552] mlx5_core :08:00.1: E-Switch: Total vports 2, per vport: max uc(1024) max mc(16384) [ 164.808886] mlx5_core :08:00.1: Port module event: module 1, Cable plugged [ 164.809228] mlx5_core :08:00.1: mlx5_pcie_event:294:(pid 292): PCIe slot advertised sufficient power (75W). [ 164.840667] mlx5_core :08:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0) [ 165.081342] mlx5_core :08:00.1: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0) [ 165.282793] mlx5_ib: Mellanox Connect-IB Infiniband driver v5.0-0 [ 165.438226] mlx5_core :08:00.0: cmd_work_handler:887:(pid 292): failed to allocate command entry [ 165.442506] infiniband rocep8s0f0: reg_mr_callback:104:(pid 292): async reg mr failed. status -11 # the following fixes this issue 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation (upstream 5.9) 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout (upstream 5.9) d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode (upstream 5.7-rc7) 3ed879965cc4 net/mlx5: net/mlx5: Use async EQ setup cleanup helpers for multiple EQs (upstream 5.6-rc1) those are on master-next branch off focal tree also synced from linux stable. (v5.4.79 upstream stable release https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907151 ) # git log --oneline Ubuntu-5.4.0-59.65..master-next 400ec5bb2816 net/mlx5: Add retry mechanism to the command entry index allocation 2bd608898edd net/mlx5: Fix a race when moving command interface to events mode bec07c488db0 net/mlx5: poll cmd EQ in case of command timeout 0c9bfdf598e1 net/mlx5: Use async EQ setup cleanup helpers for multiple EQs . I compiled master-next, booted the system with it and the issue is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
I also tested with kernel Ubuntu-4.15.0-129.132 downloaded from http://archive.ubuntu.com/ubuntu/pool/main/l/linux/ which has the commit and the issue is resolved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
William, yes, I built a bionic kernel with this commit included and the bug was resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905574] [NEW] Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
Public bug reported: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Description changed: [Impact] - unloading ib_ipoib causes a call trace to be logged in kernel buffer. + unloading ib_ipoib causes a call trace to be logged in kernel buffer. - bisecting the bionic kernel reveals that this issue was introduced by - 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() - in version 4.15.0-59.66 - + bisecting the bionic kernel reveals that this issue was discovered by + 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() + in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 - [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 + [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat
[Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Patch added: "0001-net-mlx5e-IPoIB-initialize-update_stat_work-for-ipoi.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904848/+attachment/5435933/+files/0001-net-mlx5e-IPoIB-initialize-update_stat_work-for-ipoi.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904848] [NEW] Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
Public bug reported: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was introduced by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt
[Bug 1895947] Re: backport tls-rx to ubuntu 5.8
Hi Jeff, Six additional bug fixes are needed. all applied cleanly. 94c4fed710c3 net/mlx5e: kTLS, Avoid kzalloc(GFP_KERNEL) under spinlock 581642f32f33 net/mlx5e: kTLS, Fix leak on resync error flow 66ce5fc05713 net/mlx5e: kTLS, Add missing dma_unmap in RX resync 8f0bcd19b1da net/mlx5e: TLS, Do not expose FPGA TLS counter if not supported 8b5ec43d73db net/mlx5e: Fix build break when CONFIG_XPS is not set 5831b33362fd net/mlx5e: fix memory leak of tls -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895947 Title: backport tls-rx to ubuntu 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895947] Re: backport tls-rx to ubuntu 5.8
the three bug fixes commits was accepted upstream. 6e8de0b6b469 net/mlx5e: kTLS, Fix napi sync and possible use-after-free 9c25a22dfb00 net/mlx5e: Use synchronize_rcu to sync with NAPI fe45386a2082 net/mlx5e: Use RCU to protect rq->xdp_prog ** Description changed: Hi, [Impact] The request here is to backport support for ktls-rx from upstream 5.9 to Ubuntu 20.10/20.04-HWE 5.8 kernel. [Other Info] list of required patches: (1 patch) from https://patchwork.ozlabs.org/project/netdev/patch/20200626055943.99943-3-sae...@mellanox.com/ - 2d1b69ed65ee net/mlx5: kTLS, Improve TLS params layout structures + 2d1b69ed65ee net/mlx5: kTLS, Improve TLS params layout structures (needed to apply ‘net/mlx5e: kTLS, Improve TLS feature modularity’ below cleanly) (15 patches ) - https://patchwork.ozlabs.org/project/netdev/list/?series=186181=* + https://patchwork.ozlabs.org/project/netdev/list/?series=186181=* a29074367b34 net/mlx5e: kTLS, Improve rx handler function call ed9a7c53b878 net/mlx5e: kTLS, Cleanup redundant capability check c5607360ec4e net/mlx5e: Increase Async ICO SQ size 76c1e1ac2aae net/mlx5e: kTLS, Add kTLS RX stats 0419d8c9d8f8 net/mlx5e: kTLS, Add kTLS RX resync support ed9b7646b06a net/tls: Add asynchronous resync acb5a07aaf27 Revert "net/tls: Add force_resync for driver resync" 1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support df8d866770f9 net/mlx5e: kTLS, Use kernel API to extract private offload context 7d0d0d86ec6c net/mlx5e: kTLS, Improve TLS feature modularity 5229a96e59ec net/mlx5e: Accel, Expose flow steering API for rules add/del c062d52ac24c net/mlx5e: Receive flow steering framework for accelerated TCP flows b8922a73ec3e net/mlx5e: API to manipulate TTC rules destinations c293ac927fbb net/mlx5e: Refactor build channel params 8d94b590f1e4 net/mlx5e: Turn XSK ICOSQ into a general asynchronous one - (3 bug fixes patches submitted to upstream and should be accepted soon - attached) - net/mlx5e: kTLS, Fix napi sync and possible use-after-free - net/mlx5e: Use synchronize_rcu to sync with NAPI - net/mlx5e: Use RCU to protect rq->xdp_prog + (3 bug fixes patches, also attached) + 6e8de0b6b469 net/mlx5e: kTLS, Fix napi sync and possible use-after-free + 9c25a22dfb00 net/mlx5e: Use synchronize_rcu to sync with NAPI + fe45386a2082 net/mlx5e: Use RCU to protect rq->xdp_prog - all patches are applied cleanly beside + all patches are applied cleanly beside 1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support - that has one hunk rejected in + that has one hunk rejected in file: drivers/net/ethernet/mellanox/mlx5/core/en_main.c function: mlx5e_init_nic_rx - the rejection is caused by and extra #ifdef statement - inserted by commit f4aebbfb56ed0c186adbeb2799df836da50f78e3 + the rejection is caused by and extra #ifdef statement + inserted by commit f4aebbfb56ed0c186adbeb2799df836da50f78e3 here we just need to add manually the needed lines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895947 Title: backport tls-rx to ubuntu 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894977] [NEW] IBM-iobrick patches for Ubuntu 20.04
Public bug reported:
Hi,
The request is to backport
09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during create
and destroy
with it the below list (divided to four sets) is required.
most of the patches applied cleanly above focal tree four exceptions.
1. 806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
2. b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
3. 1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying
them
4. b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
the rejected hunks need to be manually applied.
The rejected hunks are due to true<-->1 false<-->0 exchange added support for
wc (b9358bdbc713) and other minor reasons.
set 0: Unrelated code cleanups (needed for applying cleanly the mr cache set)
https://patchwork.kernel.org/cover/11170991/
909624d8db5b IB/cm: Use container_of() instead of typecast
6f26b2ac699c IB/mlx5: Remove unnecessary else statement
2d67c0798821 IB/mlx5: Remove unnecessary return statement
4b2a67362e78 RDMA/mlx5: Group boolean parameters to take less space
set 1: Rework the locking and datastructures for mlx5 implicit ODP
https://patchwork.kernel.org/cover/11181509/
46870b2391d5 RDMA/odp: Remove broken debugging call to invalidate_range
09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during
create and destroy
d561987f34f2 RDMA/mlx5: Do not store implicit children in the odp_mkeys xarray
5256edcb98a1 RDMA/mlx5: Rework implicit ODP destroy
b70d785d237c RDMA/mlx5: Avoid double lookups on the pagefault path
3389baa831b6 RDMA/mlx5: Reduce locking in implicit_mr_get_data()
423f52d65005 RDMA/mlx5: Use an xarray for the children of an implicit ODP
54375e738295 RDMA/mlx5: Split implicit handling from pagefault_mr
9162420dde49 RDMA/mlx5: Set the HW IOVA of the child MRs to their place in the
tree
c2edcd69351f RDMA/mlx5: Lift implicit_mr_alloc() into the two routines that
call it
3d5f3c54e7bc RDMA/mlx5: Rework implicit_mr_get_data
74bddb3682f6 RDMA/mlx5: Delete struct mlx5_priv->mkey_table
806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
50211ec9443f RDMA/mlx5: Split sig_err MR data into its own xarray
fb985e278a30 RDMA/mlx5: Use SRCU properly in ODP prefetch
set 2: Consolidate the mmu notifier interval_tree and locking (only first two
patches from this set)
https://patchwork.kernel.org/cover/11240081/
99cb252f5e68 mm/mmu_notifier: add an interval tree notifier
56f434f40f05 mm/mmu_notifier: define the header pre-processor parts even if
disabled
also needed for applying mr cache set cleanly.
03232cc43cff IB/mlx5: Introduce and use mkey context setting helper routine
set 3: MR cache fixes and refactoring
https://www.spinics.net/lists/linux-rdma/msg89706.html
aad719dcf379 RDMA/mlx5: Allow MRs to be created in the cache synchronously
1c78a21a0c6f RDMA/mlx5: Revise how the hysteresis scheme works for cache
filling
b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
ad2d3ef46d2a RDMA/mlx5: Lock access to ent->available_mrs/limit when doing
queue_work
a1d8854aae4e RDMA/mlx5: Fix MR cache size and limit debugfs
1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying them
b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
7c8691a396bd RDMA/mlx5: Rename the tracking variables for the MR cache
f743ff3b37df RDMA/mlx5: Replace spinlock protected write with atomic var
a3cfdd392811 {IB,net}/mlx5: Move asynchronous mkey creation to mlx5_ib
fc6a9f86f08a {IB,net}/mlx5: Assign mkey variant in mlx5_ib only
54c62e13ad76 {IB,net}/mlx5: Setup mkey variant before mr create command
invocation
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894977
Title:
IBM-iobrick patches for Ubuntu 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894977/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889625] Re: Bug fix for ktls feature
** Description changed: [IMPACT] Clearing the sock TX queue in sk_set_socket() might cause unexpected out-of-order transmit when called from sock_orphan(), as outstanding packets can pick a different TX queue and bypass the ones already queued. This is undesired in general. More specifically, it breaks the in-order scheduling property guarantee for device-offloaded TLS sockets. Remove the call to sk_tx_queue_clear() in sk_set_socket(), and add it explicitly only where needed. - [FIXES] e022f0b4a03f "net: Introduce sk_tx_queue_mapping" This cleanly cherry picks into 5.4 from 5.8. It can be checked out in my branch here: https://git.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal 1889625-mxl-ktls-bugfix [REGRESSION RISK] - + low! [TEST] + reproducing the bug is not trivial. in general terms: + nic: ConnectX6-dx with crypto enabled + send intense encrypted tcp traffic with tls offload between many clients and one server. + * clients may run on the same machine. + * clients continuously opens and closes connection to server + + at some point decryption errores might arise on some of the clients. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889625 Title: Bug fix for ktls feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889625] [NEW] Bug fix for ktls feature
Public bug reported:
The bellow upstream commit fixes a bug in Ktls feature.
It is applied cleanly above the ubuntu-focal tree and passed basic sanity
testing.
We would like it to be backported ubuntu-focal
Thanks,
Amir
commit 41b14fb8724d5a4b382a63cb4a1a61880347ccb8
Author: Tariq Toukan
Date: Mon Jun 22 23:26:04 2020 +0300
net: Do not clear the sock TX queue in sk_set_socket()
Clearing the sock TX queue in sk_set_socket() might cause unexpected
out-of-order transmit when called from sock_orphan(), as outstanding
packets can pick a different TX queue and bypass the ones already queued.
This is undesired in general. More specifically, it breaks the in-order
scheduling property guarantee for device-offloaded TLS sockets.
Remove the call to sk_tx_queue_clear() in sk_set_socket(), and add it
explicitly only where needed.
Fixes: e022f0b4a03f ("net: Introduce sk_tx_queue_mapping")
Signed-off-by: Tariq Toukan
Reviewed-by: Boris Pismenny
Signed-off-by: David S. Miller
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889625
Title:
Bug fix for ktls feature
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889625/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877270] Re: Devlink - add RoCE disable kernel support
Hi Jeff, the following patch need to be included in the patch set. 4cca96a8d9da IB/mlx5: Do reverse sequence during device removal without it devlink dev reload operation causes a double free of cache memory and leaves the kernel in a state that requires a restart. the patch is applied cleanly above ubuntu-focal tree. Thanks a lot, Amir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877270 Title: Devlink - add RoCE disable kernel support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
