** Summary changed: - Fix return value of qdisc ingress handling on success + Increase stability with connection tracking offload
** Description changed: - SRU Justification: + * Explain the bug(s) - net: Fix return value of qdisc ingress handling on success - - * Explain the bug(s) - Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. - - * brief explanation of fixes - - Fix that by setting the return value to RX success if - the packet was handled successfully. - + + Also, include set of patches to increase stability with connection + tracking offload, including reduced cpu load and possible deadlock on + cleanup. + + * What it could break. + + Packet on egress tc rule forwarding to a ingress tc rule will drop. + High cpu load. Possible deadlock on cleanup. + * How to test - - Commit msg has the steps. - - * What it could break. - - Packet on egress tc rule forwarding to a ingress tc rule will drop. - - - SRU Justification: - - netfilter: conntrack: annotate data-races around ct->timeout - netfilter: conntrack: remove unneeded nf_ct_put - netfilter: conntrack: convert to refcount_t api - netfilter: flowtable: Make sure GC works periodically in idle system - netfilter: flowtable: avoid possible false sharing - netfilter: flowtable: fix excessive hw offload attempts after failure - netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup() - netfilter: flowtable: add function to invoke garbage collection immediately - netfilter: flowtable: fix stuck flows on cleanup due to pending work - - - * Explain the bug(s) - - Set of patches to increase stability with connection tracking offload, - including reduced cpu load and possible deadlock on cleanup. - - * brief explanation of fixes - - Fix that by setting the return value to RX success if - the packet was handled successfully. - - * How to test - - Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. - - * What it could break. - - High cpu load. Possible deadlock on cleanup. + Run connection tracking hw offload scenario with millions of flows, + check cpu load, test cleanup and readd scenarios. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995004 Title: Increase stability with connection tracking offload Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. Also, include set of patches to increase stability with connection tracking offload, including reduced cpu load and possible deadlock on cleanup. * What it could break. Packet on egress tc rule forwarding to a ingress tc rule will drop. High cpu load. Possible deadlock on cleanup. * How to test Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995004/+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
