On Fri, Dec 10, 2021 at 8:52 PM Jakub Kicinski wrote:
>
> On Thu, 9 Dec 2021 09:57:33 +0200 Paul Blakey wrote:
> > @@ -238,10 +239,12 @@ void
> > skb_flow_dissect_ct(const struct sk_buff *skb,
> > struct flow_dissector *flow_dissector,
> > void
On Sun, Sep 19, 2021 at 10:44 PM Tyler Stachecki
wrote:
> Sorry if this is a no-op -- I'm admittedly not familiar with this part
> of the tree. I had added this check based on this discussion on the
> OVS mailing list:
>
On Sun, Sep 19, 2021 at 10:59 AM Tyler J. Stachecki
wrote:
>
> As of "ovs: clear skb->tstamp in forwarding path", the
> tstamp is now being cleared unconditionally to fix fq qdisc
> operation with ovs vports.
>
> While this is mostly correct and fixes forwarding for that
> use case, a slight
which can be invoked by __dp_destroy or ovs_flow_tbl_flush.
>
> Fixes: 50b0e61b32ee ("net: openvswitch: fix possible memleak on destroy
> flow-table")
> Reported-by: Johan Knöös
> Reported-at:
> https://mail.openvswitch.org/pipermail/ovs-discuss/2020-August/050489.html
&
On Mon, Aug 10, 2020 at 6:14 PM wrote:
>
> From: Tonghao Zhang
>
> To avoid some issues, for example RCU usage warning, we should
> flush the flows under ovs_lock. This patch refactors
> table_instance_destroy and introduces table_instance_flow_flush
> which can be invoked by __dp_destroy or
