1. 26 6月, 2020 1 次提交
  2. 18 2月, 2020 1 次提交
  3. 01 1月, 2020 1 次提交
  4. 09 12月, 2019 1 次提交
    • S
      batman-adv: Annotate bitwise integer pointer casts · 61a29286
      Sven Eckelmann 提交于
      The sparse commit 6002ded74587 ("add a flag to warn on casts to/from
      bitwise pointers") introduced a check for non-direct casts from/to
      restricted datatypes (when -Wbitwise-pointer is enabled).
      
      This triggered various warnings in batman-adv when some (already big
      endian) buffer content was casted to/from the corresponding big endian
      integer data types. But these were correct and can therefore be marked with
      __force to signalize sparse an intended cast from/to a bitwise type.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NSimon Wunderlich <sw@simonwunderlich.de>
      61a29286
  5. 28 11月, 2019 1 次提交
    • S
      batman-adv: Fix DAT candidate selection on little endian systems · 4cc4a170
      Sven Eckelmann 提交于
      The distributed arp table is using a DHT to store and retrieve MAC address
      information for an IP address. This is done using unicast messages to
      selected peers. The potential peers are looked up using the IP address and
      the VID.
      
      While the IP address is always stored in big endian byte order, this is not
      the case of the VID. It can (depending on the host system) either be big
      endian or little endian. The host must therefore always convert it to big
      endian to ensure that all devices calculate the same peers for the same
      lookup data.
      
      Fixes: be1db4f6 ("batman-adv: make the Distributed ARP Table vlan aware")
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NSimon Wunderlich <sw@simonwunderlich.de>
      4cc4a170
  6. 25 3月, 2019 3 次提交
  7. 07 2月, 2019 1 次提交
  8. 04 1月, 2019 1 次提交
  9. 31 12月, 2018 1 次提交
    • L
      batman-adv: Snoop DHCPACKs for DAT · b61ec31c
      Linus Lüssing 提交于
      In a 1000 nodes mesh network (Freifunk Hamburg) we can still see
      30KBit/s of ARP traffic (equalling about 25% of all layer two
      specific overhead, remaining after some filtering) flooded through
      the mesh. These 30KBit/s are mainly ARP Requests from the
      gateways / DHCP servers.
      
      By snooping DHCPACKs we can learn about MAC/IP address pairs
      in the DHCP range without relying on ARP. This patch is in preparation
      to eliminate the need for mesh wide message flooding for IPv4 address
      resolution.
      
      Also this allows to quickly update a MAC/IP pair at least in the DHT when
      DHCP reassigns an IP address to a new host.
      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>
      b61ec31c
  10. 12 11月, 2018 1 次提交
    • S
      batman-adv: Add inconsistent dat netlink dump detection · 6f81652a
      Sven Eckelmann 提交于
      The netlink dump functionality transfers a large number of entries from the
      kernel to userspace. It is rather likely that the transfer has to
      interrupted and later continued. During that time, it can happen that
      either new entries are added or removed. The userspace could than either
      receive some entries multiple times or miss entries.
      
      Commit 670dc283 ("netlink: advertise incomplete dumps") introduced a
      mechanism to inform userspace about this problem. Userspace can then decide
      whether it is necessary or not to retry dumping the information again.
      
      The netlink dump functions have to be switched to exclusive locks to avoid
      changes while the current message is prepared. The already existing
      generation sequence counter from the hash helper can be used for this
      simple hash.
      Reported-by: NMatthias Schiffer <mschiffer@universe-factory.net>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NSimon Wunderlich <sw@simonwunderlich.de>
      6f81652a
  11. 17 3月, 2018 1 次提交
  12. 14 3月, 2018 1 次提交
  13. 27 2月, 2018 2 次提交
  14. 16 12月, 2017 3 次提交
  15. 28 9月, 2017 1 次提交
  16. 29 7月, 2017 1 次提交
  17. 23 5月, 2017 1 次提交
  18. 19 5月, 2017 1 次提交
  19. 05 4月, 2017 1 次提交
  20. 26 3月, 2017 1 次提交
  21. 22 3月, 2017 2 次提交
  22. 17 3月, 2017 1 次提交
  23. 26 1月, 2017 1 次提交
  24. 19 1月, 2017 1 次提交
    • T
      net: Remove usage of net_device last_rx member · 4a7c9726
      Tobias Klauser 提交于
      The network stack no longer uses the last_rx member of struct net_device
      since the bonding driver switched to use its own private last_rx in
      commit 9f242738 ("bonding: use last_arp_rx in slave_last_rx()").
      
      However, some drivers still (ab)use the field for their own purposes and
      some driver just update it without actually using it.
      
      Previously, there was an accompanying comment for the last_rx member
      added in commit 4dc89133 ("net: add a comment on netdev->last_rx")
      which asked drivers not to update is, unless really needed. However,
      this commend was removed in commit f8ff080d ("bonding: remove
      useless updating of slave->dev->last_rx"), so some drivers added later
      on still did update last_rx.
      
      Remove all usage of last_rx and switch three drivers (sky2, atp and
      smc91c92_cs) which actually read and write it to use their own private
      copy in netdev_priv.
      
      Compile-tested with allyesconfig and allmodconfig on x86 and arm.
      
      Cc: Eric Dumazet <eric.dumazet@gmail.com>
      Cc: Jay Vosburgh <j.vosburgh@gmail.com>
      Cc: Veaceslav Falico <vfalico@gmail.com>
      Cc: Andy Gospodarek <andy@greyhouse.net>
      Cc: Mirko Lindner <mlindner@marvell.com>
      Cc: Stephen Hemminger <stephen@networkplumber.org>
      Signed-off-by: NTobias Klauser <tklauser@distanz.ch>
      Acked-by: NEric Dumazet <edumazet@google.com>
      Reviewed-by: NJay Vosburgh <jay.vosburgh@canonical.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4a7c9726
  25. 30 10月, 2016 1 次提交
  26. 17 10月, 2016 1 次提交
  27. 09 8月, 2016 2 次提交
  28. 05 7月, 2016 1 次提交
  29. 30 6月, 2016 2 次提交
  30. 10 5月, 2016 1 次提交
  31. 04 5月, 2016 2 次提交