Skip to content
  • Kirill Tkhai's avatar
    net: Don't take rtnl_lock() in wireless_nlevent_flush() · 10256deb
    Kirill Tkhai authored
    
    
    This function iterates over net_namespace_list and flushes
    the queue for every of them. What does this rtnl_lock()
    protects?! Since we may add skbs to net::wext_nlevents
    without rtnl_lock(), it does not protects us about queuers.
    
    It guarantees, two threads can't flush the queue in parallel,
    that can change the order, but since skb can be queued
    in any order, it doesn't matter, how many threads do this
    in parallel. In case of several threads, this will be even
    faster.
    
    So, we can remove rtnl_lock() here, as it was used for
    iteration over net_namespace_list only.
    
    Signed-off-by: default avatarKirill Tkhai <ktkhai@virtuozzo.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    10256deb