1. 05 10月, 2011 1 次提交
  2. 28 7月, 2011 1 次提交
    • N
      net: Audit drivers to identify those needing IFF_TX_SKB_SHARING cleared · 550fd08c
      Neil Horman 提交于
      After the last patch, We are left in a state in which only drivers calling
      ether_setup have IFF_TX_SKB_SHARING set (we assume that drivers touching real
      hardware call ether_setup for their net_devices and don't hold any state in
      their skbs.  There are a handful of drivers that violate this assumption of
      course, and need to be fixed up.  This patch identifies those drivers, and marks
      them as not being able to support the safe transmission of skbs by clearning the
      IFF_TX_SKB_SHARING flag in priv_flags
      Signed-off-by: NNeil Horman <nhorman@tuxdriver.com>
      CC: Karsten Keil <isdn@linux-pingi.de>
      CC: "David S. Miller" <davem@davemloft.net>
      CC: Jay Vosburgh <fubar@us.ibm.com>
      CC: Andy Gospodarek <andy@greyhouse.net>
      CC: Patrick McHardy <kaber@trash.net>
      CC: Krzysztof Halasa <khc@pm.waw.pl>
      CC: "John W. Linville" <linville@tuxdriver.com>
      CC: Greg Kroah-Hartman <gregkh@suse.de>
      CC: Marcel Holtmann <marcel@holtmann.org>
      CC: Johannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      550fd08c
  3. 22 7月, 2011 1 次提交
  4. 07 6月, 2011 1 次提交
  5. 23 5月, 2011 1 次提交
  6. 21 5月, 2011 1 次提交
  7. 20 5月, 2011 1 次提交
  8. 10 5月, 2011 1 次提交
    • E
      net: use batched device unregister in veth and macvlan · 226bd341
      Eric Dumazet 提交于
      veth devices dont use the batched device unregisters yet.
      
      Since veth are a pair of devices, it makes sense to use a batch of two
      unregisters, this roughly divides dismantle time by two.
      
      Fix this by changing dellink() callers to always provide a non NULL
      head. (Idea from Michał Mirosław)
      
      This patch also handles macvlan case : We now dismantle all macvlans on
      top of a lower dev at once.
      Reported-by: NAlex Bligh <alex@alex.org.uk>
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Cc: Michał Mirosław <mirqus@gmail.com>
      Cc: Jesse Gross <jesse@nicira.com>
      Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Ben Greear <greearb@candelatech.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      226bd341
  9. 08 5月, 2011 1 次提交
  10. 18 4月, 2011 1 次提交
  11. 22 3月, 2011 1 次提交
    • E
      macvlan: Fix use after free of struct macvlan_port. · d5cd9244
      Eric W. Biederman 提交于
      When the macvlan driver was extended to call unregisgter_netdevice_queue
      in 23289a37, a use after free of struct
      macvlan_port was introduced.  The code in dellink relied on unregister_netdevice
      actually unregistering the net device so it would be safe to free macvlan_port.
      
      Since unregister_netdevice_queue can just queue up the unregister instead of
      performing the unregiser immediately we free the macvlan_port too soon and
      then the code in macvlan_stop removes the macaddress for the set of macaddress
      to listen for and uses memory that has already been freed.
      
      To fix this add a reference count to track when it is safe to free the macvlan_port
      and move the call of macvlan_port_destroy into macvlan_uninit which is guaranteed
      to be called after the final macvlan_port_close.
      Signed-off-by: NEric W. Biederman <ebiederm@aristanetworks.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d5cd9244
  12. 17 3月, 2011 1 次提交
  13. 15 3月, 2011 1 次提交
    • D
      macvlan : fix checksums error when we are in bridge mode · 12a2856b
      Daniel Lezcano 提交于
      When the lower device has offloading capabilities, the packets checksums
      are not computed. That leads to have any macvlan port in bridge mode to
      not work because the packets are dropped due to a bad checksum.
      
      If the macvlan is in bridge mode, the packet is forwarded to another
      macvlan port and reach the network stack where it looks for a checksum
      but this one was not computed due to the offloading of the lower device.
      In this case, we have to set the packet with CHECKSUM_UNNECESSARY
      when it is forwarded to a bridged port and restore the previous value of
      ip_summed when the packet goes to the lowerdev.
      Signed-off-by: NDaniel Lezcano <daniel.lezcano@free.fr>
      Cc: Patrick McHardy <kaber@trash.net>
      Cc: Andrian Nord <nightnord@gmail.com>
      Acked-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      12a2856b
  14. 23 11月, 2010 1 次提交
    • S
      macvlan: Introduce 'passthru' mode to takeover the underlying device · eb06acdc
      Sridhar Samudrala 提交于
      With the current default 'vepa' mode, a KVM guest using virtio with
      macvtap backend has the following limitations.
      - cannot change/add a mac address on the guest virtio-net
      - cannot create a vlan device on the guest virtio-net
      - cannot enable promiscuous mode on guest virtio-net
      
      To address these limitations, this patch introduces a new mode called
      'passthru' when creating a macvlan device which allows takeover of the
      underlying device and passing it to a guest using virtio with macvtap
      backend.
      
      Only one macvlan device is allowed in passthru mode and it inherits
      the mac address from the underlying device and sets it in promiscuous
      mode to receive and forward all the packets.
      Signed-off-by: NSridhar Samudrala <sri@us.ibm.com>
      
      -------------------------------------------------------------------------
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      eb06acdc
  15. 17 11月, 2010 1 次提交
    • E
      macvlan: lockless tx path · 8ffab51b
      Eric Dumazet 提交于
      macvlan is a stacked device, like tunnels. We should use the lockless
      mechanism we are using in tunnels and loopback.
      
      This patch completely removes locking in TX path.
      
      tx stat counters are added into existing percpu stat structure, renamed
      from rx_stats to pcpu_stats.
      
      Note : this reverts commit 2c114553 (macvlan: add multiqueue
      capability)
      
      Note : rx_errors converted to a 32bit counter, like tx_dropped, since
      they dont need 64bit range.
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Cc: Patrick McHardy <kaber@trash.net>
      Cc: Ben Greear <greearb@candelatech.com>
      Cc: Ben Hutchings <bhutchings@solarflare.com>
      Acked-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8ffab51b
  16. 18 9月, 2010 1 次提交
  17. 28 7月, 2010 1 次提交
  18. 23 7月, 2010 1 次提交
    • H
      macvtap: Limit packet queue length · 8a35747a
      Herbert Xu 提交于
      Mark Wagner reported OOM symptoms when sending UDP traffic over
      a macvtap link to a kvm receiver.
      
      This appears to be caused by the fact that macvtap packet queues
      are unlimited in length.  This means that if the receiver can't
      keep up with the rate of flow, then we will hit OOM. Of course
      it gets worse if the OOM killer then decides to kill the receiver.
      
      This patch imposes a cap on the packet queue length, in the same
      way as the tuntap driver, using the device TX queue length.
      
      Please note that macvtap currently has no way of giving congestion
      notification, that means the software device TX queue cannot be
      used and packets will always be dropped once the macvtap driver
      queue fills up.
      
      This shouldn't be a great problem for the scenario where macvtap
      is used to feed a kvm receiver, as the traffic is most likely
      external in origin so congestion notification can't be applied
      anyway.
      
      Of course, if anybody decides to complain about guest-to-guest
      UDP packet loss down the track, then we may have to revisit this.
      
      Incidentally, this patch also fixes a real memory leak when
      macvtap_get_queue fails.
      
      Chris Wright noticed that for this patch to work, we need a
      non-zero TX queue length.  This patch includes his work to change
      the default macvtap TX queue length to 500.
      Reported-by: NMark Wagner <mwagner@redhat.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Acked-by: NChris Wright <chrisw@sous-sol.org>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8a35747a
  19. 10 7月, 2010 1 次提交
    • B
      net: Get rid of rtnl_link_stats64 / net_device_stats union · 3cfde79c
      Ben Hutchings 提交于
      In commit be1f3c2c "net: Enable 64-bit
      net device statistics on 32-bit architectures" I redefined struct
      net_device_stats so that it could be used in a union with struct
      rtnl_link_stats64, avoiding the need for explicit copying or
      conversion between the two.  However, this is unsafe because there is
      no locking required and no lock consistently held around calls to
      dev_get_stats() and use of the statistics structure it returns.
      
      In commit 28172739 "net: fix 64 bit
      counters on 32 bit arches" Eric Dumazet dealt with that problem by
      requiring callers of dev_get_stats() to provide storage for the
      result.  This means that the net_device::stats64 field and the padding
      in struct net_device_stats are now redundant, so remove them.
      
      Update the comment on net_device_ops::ndo_get_stats64 to reflect its
      new usage.
      
      Change dev_txq_stats_fold() to use struct rtnl_link_stats64, since
      that is what all its callers are really using and it is no longer
      going to be compatible with struct net_device_stats.
      
      Eric Dumazet suggested the separate function for the structure
      conversion.
      Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
      Acked-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3cfde79c
  20. 08 7月, 2010 1 次提交
    • E
      net: fix 64 bit counters on 32 bit arches · 28172739
      Eric Dumazet 提交于
      There is a small possibility that a reader gets incorrect values on 32
      bit arches. SNMP applications could catch incorrect counters when a
      32bit high part is changed by another stats consumer/provider.
      
      One way to solve this is to add a rtnl_link_stats64 param to all
      ndo_get_stats64() methods, and also add such a parameter to
      dev_get_stats().
      
      Rule is that we are not allowed to use dev->stats64 as a temporary
      storage for 64bit stats, but a caller provided area (usually on stack)
      
      Old drivers (only providing get_stats() method) need no changes.
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      28172739
  21. 29 6月, 2010 1 次提交
  22. 16 6月, 2010 2 次提交
  23. 08 6月, 2010 1 次提交
  24. 02 6月, 2010 1 次提交
  25. 25 5月, 2010 1 次提交
  26. 16 5月, 2010 2 次提交
  27. 04 4月, 2010 1 次提交
  28. 19 3月, 2010 1 次提交
  29. 04 2月, 2010 2 次提交
  30. 16 1月, 2010 1 次提交
  31. 04 12月, 2009 1 次提交
  32. 27 11月, 2009 3 次提交
    • A
      macvlan: export macvlan mode through netlink · 27c0b1a8
      Arnd Bergmann 提交于
      In order to support all three modes of macvlan at
      runtime, extend the existing netlink protocol
      to allow choosing the mode per macvlan slave
      interface.
      
      This depends on a matching patch to iproute2
      in order to become accessible in user land.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      27c0b1a8
    • A
      macvlan: implement bridge, VEPA and private mode · 618e1b74
      Arnd Bergmann 提交于
      This allows each macvlan slave device to be in one
      of three modes, depending on the use case:
      
      MACVLAN_PRIVATE:
        The device never communicates with any other device
        on the same upper_dev. This even includes frames
        coming back from a reflective relay, where supported
        by the adjacent bridge.
      
      MACVLAN_VEPA:
        The new Virtual Ethernet Port Aggregator (VEPA) mode,
        we assume that the adjacent bridge returns all frames
        where both source and destination are local to the
        macvlan port, i.e. the bridge is set up as a reflective
        relay.
        Broadcast frames coming in from the upper_dev get
        flooded to all macvlan interfaces in VEPA mode.
        We never deliver any frames locally.
      
      MACVLAN_BRIDGE:
        We provide the behavior of a simple bridge between
        different macvlan interfaces on the same port. Frames
        from one interface to another one get delivered directly
        and are not sent out externally. Broadcast frames get
        flooded to all other bridge ports and to the external
        interface, but when they come back from a reflective
        relay, we don't deliver them again.
        Since we know all the MAC addresses, the macvlan bridge
        mode does not require learning or STP like the bridge
        module does.
      
      Based on an earlier patch "macvlan: Reflect macvlan packets
      meant for other macvlan devices" by Eric Biederman.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NPatrick McHardy <kaber@trash.net>
      Cc: Eric Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      618e1b74
    • A
      macvlan: cleanup rx statistics · a1e514c5
      Arnd Bergmann 提交于
      We have very similar code for rx statistics in
      two places in the macvlan driver, with a third
      one being added in the next patch.
      
      Consolidate them into one function to improve
      overall readability of the driver.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a1e514c5
  33. 24 11月, 2009 1 次提交
  34. 18 11月, 2009 1 次提交
    • E
      macvlan: Precise RX stats accounting · fccaf710
      Eric Dumazet 提交于
      With multi queue devices, its possible that several cpus call
      macvlan RX routines simultaneously for the same macvlan device.
      
      We update RX stats counter without any locking, so we can
      get slightly wrong counters.
      
      One possible fix is to use percpu counters, to get precise
      accounting and also get guarantee of no cache line ping pongs
      between cpus.
      
      Note: this adds 16 bytes (32 bytes on 64bit arches) of percpu
      data per macvlan device.
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fccaf710
  35. 14 11月, 2009 1 次提交