Re: [PATCH net-next] vxlan: Do not assume RTNL is held in vxlan_fdb_info()

From: Ido Schimmel Date: Mon, 25 May 2020 00:38:56 +0300 > From: Ido Schimmel > > vxlan_fdb_info() is not always called with RTNL held or from an RCU > read-side critical section. For example, in the following call path: > > vxlan_cleanup() > vxlan_fdb_destroy() > vxlan_fdb_notify() >

Re: [PATCH net-next] vxlan: Do not assume RTNL is held in vxlan_fdb_info()

On Sun, May 24, 2020 at 2:39 PM Ido Schimmel wrote: > > From: Ido Schimmel > > vxlan_fdb_info() is not always called with RTNL held or from an RCU > read-side critical section. For example, in the following call path: > > vxlan_cleanup() > vxlan_fdb_destroy() > vxlan_fdb_notify() > __

[PATCH net-next] vxlan: Do not assume RTNL is held in vxlan_fdb_info()

From: Ido Schimmel vxlan_fdb_info() is not always called with RTNL held or from an RCU read-side critical section. For example, in the following call path: vxlan_cleanup() vxlan_fdb_destroy() vxlan_fdb_notify() __vxlan_fdb_notify() vxlan_fdb_info() The use of rtnl_dereferenc