lkml.org 
[lkml]   [2014]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Multitude of dst obsolescense race conditions
From
Date
On Fri, 2014-06-06 at 11:12 -0700, Paul E. McKenney wrote:

> It is probably just be me getting lost in the code, but I am not seeing
> a synchronize_rcu(), call_rcu(), or synchronize_net() anywhere in
> dst_release() or the things that it calls. If there really isn't such
> a call, then I don't see how the above code is safe in the case where
> __sk_dst_set() is invoked on one CPU just after sk_dst_get() executes
> the rcu_dereference() on some other CPU.

Well, this part is fine, dst_release() do not free dst that are
potentially stored in sk_dst_cache

Only the refcount is decremented.

The bug is elsewhere, we had another thread raising this issue on netdev
this morning.

I am cooking a patch to clear the mess.

Thanks




\
 
 \ /
  Last update: 2014-06-06 21:21    [W:0.093 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site