Thread (12 messages) 12 messages, 2 authors, 2013-05-31

Re: [Patch net-next] vxlan: do real refcnt for vn_sock

From: Cong Wang <hidden>
Date: 2013-05-29 02:09:01

On Tue, 2013-05-28 at 08:22 -0700, Stephen Hemminger wrote:
On Tue, 28 May 2013 19:07:22 +0800
Cong Wang [off-list ref] wrote:
quoted
From: Cong Wang <redacted>

In commit 553675fb5e9ce3d71a (vxlan: listen on multiple ports),
we use kfree_rcu() to free ->vn_sock, but a) there is no use
of RCU API to access this filed, b) RCU is not enough to do refcnt
here, because in vxlan_leave_group() we drop RTNL lock before
locking the socket, it could be possible that this field is
freed during this period.

So, instead making things complex, just do basic refcnt for
the ->vn_sock, like we do for others.
...
Not needed all access is under RTNL
I know, this is why I had a patch (not posted) which adds the missing
rtnl_dereference(), but even if we had these, it is still not correct.

As I explained in the changelog, vxlan_leave_group() has a problem,
because it releases rtnl lock before locking the socket, _and_ it is
called after vxlan_dellink() which schedules a work to cleanup the
struct. Therefore the ->vn_sock could be freed right after rtnl lock is
released.

Am I miss anything?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help