1. 18 3月, 2018 1 次提交
  2. 17 3月, 2018 1 次提交
  3. 22 12月, 2017 1 次提交
  4. 16 12月, 2017 3 次提交
  5. 28 9月, 2017 1 次提交
  6. 23 5月, 2017 1 次提交
  7. 19 5月, 2017 1 次提交
  8. 22 3月, 2017 2 次提交
  9. 26 1月, 2017 2 次提交
  10. 09 11月, 2016 4 次提交
  11. 30 10月, 2016 2 次提交
    • S
      batman-adv: Consume skb in batadv_send_skb_to_orig · 1ad5bcb2
      Sven Eckelmann 提交于
      Sending functions in Linux consume the supplied skbuff. Doing the same in
      batadv_send_skb_to_orig avoids the hack of returning -1 (-EPERM) to signal
      the caller that he is responsible for cleaning up the skb.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NSimon Wunderlich <sw@simonwunderlich.de>
      1ad5bcb2
    • L
      batman-adv: Simple (re)broadcast avoidance · 3111beed
      Linus Lüssing 提交于
      With this patch, (re)broadcasting on a specific interfaces is avoided:
      
      * No neighbor: There is no need to broadcast on an interface if there
        is no node behind it.
      
      * Single neighbor is source: If there is just one neighbor on an
        interface and if this neighbor is the one we actually got this
        broadcast packet from, then we do not need to echo it back.
      
      * Single neighbor is originator: If there is just one neighbor on
        an interface and if this neighbor is the originator of this
        broadcast packet, then we do not need to echo it back.
      
      Goodies for BATMAN V:
      
      ("Upgrade your BATMAN IV network to V now to get these for free!")
      
      Thanks to the split of OGMv1 into two packet types, OGMv2 and ELP
      that is, we can now apply the same optimizations stated above to OGMv2
      packets, too.
      
      Furthermore, with BATMAN V, rebroadcasts can be reduced in certain
      multi interface cases, too, where BATMAN IV cannot. This is thanks to
      the removal of the "secondary interface originator" concept in BATMAN V.
      Signed-off-by: NLinus Lüssing <linus.luessing@c0d3.blue>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NSimon Wunderlich <sw@simonwunderlich.de>
      3111beed
  12. 26 8月, 2016 1 次提交
  13. 09 8月, 2016 1 次提交
  14. 05 7月, 2016 1 次提交
  15. 04 7月, 2016 3 次提交
  16. 30 6月, 2016 5 次提交
  17. 29 6月, 2016 1 次提交
  18. 13 6月, 2016 1 次提交
  19. 18 5月, 2016 1 次提交
  20. 10 5月, 2016 3 次提交
  21. 24 4月, 2016 1 次提交
    • S
      batman-adv: Reduce refcnt of removed router when updating route · d1a65f17
      Sven Eckelmann 提交于
      _batadv_update_route rcu_derefences orig_ifinfo->router outside of a
      spinlock protected region to print some information messages to the debug
      log. But this pointer is not checked again when the new pointer is assigned
      in the spinlock protected region. Thus is can happen that the value of
      orig_ifinfo->router changed in the meantime and thus the reference counter
      of the wrong router gets reduced after the spinlock protected region.
      
      Just rcu_dereferencing the value of orig_ifinfo->router inside the spinlock
      protected region (which also set the new pointer) is enough to get the
      correct old router object.
      
      Fixes: e1a5382f ("batman-adv: Make orig_node->router an rcu protected pointer")
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NMarek Lindner <mareklindner@neomailbox.ch>
      Signed-off-by: NAntonio Quartulli <a@unstable.cc>
      d1a65f17
  22. 23 2月, 2016 3 次提交