[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200813.155348.1997626107228415421.davem@davemloft.net>
Date: Thu, 13 Aug 2020 15:53:48 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: xiangxia.m.yue@...il.com
Cc: joel@...lfernandes.org, jknoos@...gle.com, gvrose8192@...il.com,
urezki@...il.com, paulmck@...nel.org, dev@...nvswitch.org,
netdev@...r.kernel.org, rcu@...r.kernel.org
Subject: Re: [PATCH v2] net: openvswitch: introduce common code for
flushing flows
From: xiangxia.m.yue@...il.com
Date: Wed, 12 Aug 2020 17:56:39 +0800
> From: Tonghao Zhang <xiangxia.m.yue@...il.com>
>
> To avoid some issues, for example RCU usage warning and double free,
> 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 ovs_flow_tbl_flush.
>
> Fixes: 50b0e61b32ee ("net: openvswitch: fix possible memleak on destroy flow-table")
> Reported-by: Johan Knöös <jknoos@...gle.com>
> Reported-at: https://mail.openvswitch.org/pipermail/ovs-discuss/2020-August/050489.html
> Signed-off-by: Tonghao Zhang <xiangxia.m.yue@...il.com>
Applied, thank you.
Powered by blists - more mailing lists