18 Apr, 2019

1 commit


03 Apr, 2019

1 commit

  • [ Upstream commit c22da36688d6298f2e546dcc43fdc1ad35036467 ]

    Similarly to commit a7603ac1fc8c ("geneve: change NET_UDP_TUNNEL
    dependency to select"), GTP has a dependency on NET_UDP_TUNNEL which
    makes impossible to compile it if no other protocol depending on
    NET_UDP_TUNNEL is selected.

    Fix this by changing the depends to a select, and drop NET_IP_TUNNEL from
    the select list, as it already depends on NET_UDP_TUNNEL.

    Signed-off-by: Matteo Croce
    Signed-off-by: David S. Miller
    Signed-off-by: Greg Kroah-Hartman

    Matteo Croce
     

29 May, 2018

2 commits

  • This patch enables virtio_net to switch over to a VF datapath when STANDBY
    feature is enabled and a VF netdev is present with the same MAC address.
    It allows live migration of a VM with a direct attached VF without the need
    to setup a bond/team between a VF and virtio net device in the guest.

    It uses the API that is exported by the net_failover driver to create and
    and destroy a master failover netdev. When STANDBY feature is enabled, an
    additional netdev(failover netdev) is created that acts as a master device
    and tracks the state of the 2 lower netdevs. The original virtio_net netdev
    is marked as 'standby' netdev and a passthru device with the same MAC is
    registered as 'primary' netdev.

    The hypervisor needs to unplug the VF device from the guest on the source
    host and reset the MAC filter of the VF to initiate failover of datapath
    to virtio before starting the migration. After the migration is completed,
    the destination hypervisor sets the MAC filter on the VF and plugs it back
    to the guest to switch over to VF datapath.

    This patch is based on the discussion initiated by Jesse on this thread.
    https://marc.info/?l=linux-virtualization&m=151189725224231&w=2

    Signed-off-by: Sridhar Samudrala
    Signed-off-by: David S. Miller

    Sridhar Samudrala
     
  • The net_failover driver provides an automated failover mechanism via APIs
    to create and destroy a failover master netdev and manages a primary and
    standby slave netdevs that get registered via the generic failover
    infrastructure.

    The failover netdev acts a master device and controls 2 slave devices. The
    original paravirtual interface gets registered as 'standby' slave netdev and
    a passthru/vf device with the same MAC gets registered as 'primary' slave
    netdev. Both 'standby' and 'failover' netdevs are associated with the same
    'pci' device. The user accesses the network interface via 'failover' netdev.
    The 'failover' netdev chooses 'primary' netdev as default for transmits when
    it is available with link up and running.

    This can be used by paravirtual drivers to enable an alternate low latency
    datapath. It also enables hypervisor controlled live migration of a VM with
    direct attached VF by failing over to the paravirtual datapath when the VF
    is unplugged.

    Signed-off-by: Sridhar Samudrala
    Signed-off-by: David S. Miller

    Sridhar Samudrala
     

28 Apr, 2018

1 commit

  • Commit c40e89fd358e ("geneve: configure MTU based on a lower device") added
    an IS_ENABLED(CONFIG_IPV6) to geneve, leading to the following link error
    with CONFIG_GENEVE=y and CONFIG_IPV6=m:

    drivers/net/geneve.o: In function `geneve_link_config':
    geneve.c:(.text+0x14c): undefined reference to `rt6_lookup'

    Fix this by adding a Kconfig dependency and forcing GENEVE to be a module
    when IPV6 is a module.

    Fixes: c40e89fd358e ("geneve: configure MTU based on a lower device")
    Signed-off-by: Tobias Regnery
    Signed-off-by: David S. Miller

    Tobias Regnery
     

30 Mar, 2018

1 commit

  • Add devlink support to netdevsim and use it to implement a simple,
    profile based resource controller. Only one controller is needed
    per namespace, so the first netdevsim netdevice in a namespace
    registers with devlink. If that device is deleted, the resource
    settings are deleted.

    The resource controller allows a user to limit the number of IPv4 and
    IPv6 FIB entries and FIB rules. The resource paths are:
    /IPv4
    /IPv4/fib
    /IPv4/fib-rules
    /IPv6
    /IPv6/fib
    /IPv6/fib-rules

    The IPv4 and IPv6 top level resources are unlimited in size and can not
    be changed. From there, the number of FIB entries and FIB rule entries
    are unlimited by default. A user can specify a limit for the fib and
    fib-rules resources:

    $ devlink resource set netdevsim/netdevsim0 path /IPv4/fib size 96
    $ devlink resource set netdevsim/netdevsim0 path /IPv4/fib-rules size 16
    $ devlink resource set netdevsim/netdevsim0 path /IPv6/fib size 64
    $ devlink resource set netdevsim/netdevsim0 path /IPv6/fib-rules size 16
    $ devlink dev reload netdevsim/netdevsim0

    such that the number of rules or routes is limited (96 ipv4 routes in the
    example above):
    $ for n in $(seq 1 32); do ip ro add 10.99.$n.0/24 dev eth1; done
    Error: netdevsim: Exceeded number of supported fib entries.

    $ devlink resource show netdevsim/netdevsim0
    netdevsim/netdevsim0:
    name IPv4 size unlimited unit entry size_min 0 size_max unlimited size_gran 1 dpipe_tables non
    resources:
    name fib size 96 occ 96 unit entry size_min 0 size_max unlimited size_gran 1 dpipe_tables
    ...

    With this template in place for resource management, it is fairly trivial
    to extend and shows one way to implement a simple counter based resource
    controller typical of network profiles.

    Currently, devlink only supports initial namespace. Code is in place to
    adapt netdevsim to a per namespace controller once the network namespace
    issues are resolved.

    Signed-off-by: David Ahern
    Signed-off-by: David S. Miller

    David Ahern
     

27 Feb, 2018

1 commit

  • We no longer depend on IPV6, but that now causes a link error with
    CONFIG_IPV6=m and CONFIG_IPVLAN=y:

    drivers/net/ipvlan/ipvlan_core.o: In function `ipvlan_queue_xmit':
    ipvlan_core.c:(.text+0x1440): undefined reference to `ip6_route_output_flags'
    drivers/net/ipvlan/ipvlan_core.o: In function `ipvlan_l3_rcv':
    ipvlan_core.c:(.text+0x1818): undefined reference to `ip6_route_input_lookup'

    This adds back the dependency on IPV6, with the option of building without
    IPV6, but forcing IPVLAN to be a module when IPV6 is a module.

    Fixes: 94333fac44d1 ("ipvlan: drop ipv6 dependency")
    Signed-off-by: Arnd Bergmann
    Signed-off-by: David S. Miller

    Arnd Bergmann
     

22 Feb, 2018

2 commits


03 Dec, 2017

1 commit

  • To be able to run selftests without any hardware required we
    need a software model. The model can also serve as an example
    implementation for those implementing actual HW offloads.
    The dummy driver have previously been extended to test SR-IOV,
    but the general consensus seems to be against adding further
    features to it.

    Add a new driver for purposes of software modelling only.
    eBPF and SR-IOV will be added here shortly, others are invited
    to further extend the driver with their offload models.

    Signed-off-by: Jakub Kicinski
    Reviewed-by: Simon Horman
    Reviewed-by: Quentin Monnet
    Signed-off-by: Daniel Borkmann

    Jakub Kicinski
     

03 Oct, 2017

1 commit

  • ThunderboltIP is a protocol created by Apple to tunnel IP/ethernet
    traffic over a Thunderbolt cable. The protocol consists of configuration
    phase where each side sends ThunderboltIP login packets (the protocol is
    determined by UUID in the XDomain packet header) over the configuration
    channel. Once both sides get positive acknowledgment to their login
    packet, they configure high-speed DMA path accordingly. This DMA path is
    then used to transmit and receive networking traffic.

    This patch creates a virtual ethernet interface the host software can
    use in the same way as any other networking interface. Once the
    interface is brought up successfully network packets get tunneled over
    the Thunderbolt cable to the remote host and back.

    The connection is terminated by sending a ThunderboltIP logout packet
    over the configuration channel. We do this when the network interface is
    brought down by user or the driver is unloaded.

    Signed-off-by: Amir Levy
    Signed-off-by: Michael Jamet
    Signed-off-by: Mika Westerberg
    Reviewed-by: Yehezkel Bernat
    Reviewed-by: Andy Shevchenko
    Signed-off-by: David S. Miller

    Amir Levy
     

24 Aug, 2017

1 commit

  • Lguest seems to be rather unused these days. It has seen only patches
    ensuring it still builds the last two years and its official state is
    "Odd Fixes".

    Remove it in order to be able to clean up the paravirt code.

    Signed-off-by: Juergen Gross
    Acked-by: Rusty Russell
    Acked-by: Thomas Gleixner
    Cc: Linus Torvalds
    Cc: Peter Zijlstra
    Cc: boris.ostrovsky@oracle.com
    Cc: lguest@lists.ozlabs.org
    Cc: rusty@rustcorp.com.au
    Cc: xen-devel@lists.xenproject.org
    Link: http://lkml.kernel.org/r/20170816173157.8633-3-jgross@suse.com
    Signed-off-by: Ingo Molnar

    Juergen Gross
     

25 Apr, 2017

1 commit

  • Add vsockmon virtual network device that receives packets from the vsock
    transports and exposes them to user space.

    Based on the nlmon device.

    Signed-off-by: Gerard Garcia
    Signed-off-by: Stefan Hajnoczi
    Signed-off-by: David S. Miller

    Gerard Garcia
     

18 Feb, 2017

1 commit

  • I got a warning about broken code on ARM64 with 64K pages:

    drivers/net/vmxnet3/vmxnet3_drv.c: In function 'vmxnet3_rq_init':
    drivers/net/vmxnet3/vmxnet3_drv.c:1679:29: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
    rq->buf_info[0][i].len = PAGE_SIZE;

    'len' here is a 16-bit integer, so this clearly won't work. I don't think
    this driver is used much on anything other than x86, so there is no need
    to fix this properly and we can work around it with a Kconfig dependency
    to forbid known-broken configurations. qemu in theory supports it on
    other architectures too, but presumably only for compatibility with x86
    guests that also run on vmware.

    CONFIG_PAGE_SIZE_64KB is used on hexagon, mips, sh and tile, the other
    symbols are architecture-specific names for the same thing.

    Signed-off-by: Arnd Bergmann
    Signed-off-by: David S. Miller

    Arnd Bergmann
     

12 Feb, 2017

2 commits

  • This patch adds a tap character device driver that is based on the
    IP-VLAN network interface, called ipvtap. An ipvtap device can be created
    in the same way as an ipvlan device, using 'type ipvtap', and then accessed
    using the tap user space interface.

    Signed-off-by: Sainath Grandhi
    Signed-off-by: David S. Miller

    Sainath Grandhi
     
  • This patch makes tap a separate module for other types of virtual interfaces, for example,
    ipvlan to use.

    Signed-off-by: Sainath Grandhi
    Signed-off-by: David S. Miller

    Sainath Grandhi
     

09 Feb, 2017

1 commit


21 Sep, 2016

1 commit

  • kbuild-build-bot reported that if NETFILTER is not selected, the
    build fails pointing to netfilter symbols.

    Fixes: 4fbae7d83c98 ("ipvlan: Introduce l3s mode")

    Signed-off-by: Mahesh Bandewar
    Signed-off-by: David S. Miller

    Mahesh Bandewar
     

19 Sep, 2016

1 commit

  • In a typical IPvlan L3 setup where master is in default-ns and
    each slave is into different (slave) ns. In this setup egress
    packet processing for traffic originating from slave-ns will
    hit all NF_HOOKs in slave-ns as well as default-ns. However same
    is not true for ingress processing. All these NF_HOOKs are
    hit only in the slave-ns skipping them in the default-ns.
    IPvlan in L3 mode is restrictive and if admins want to deploy
    iptables rules in default-ns, this asymmetric data path makes it
    impossible to do so.

    This patch makes use of the l3_rcv() (added as part of l3mdev
    enhancements) to perform input route lookup on RX packets without
    changing the skb->dev and then uses nf_hook at NF_INET_LOCAL_IN
    to change the skb->dev just before handing over skb to L4.

    Signed-off-by: Mahesh Bandewar
    CC: David Ahern
    Reviewed-by: David Ahern
    Signed-off-by: David S. Miller

    Mahesh Bandewar
     

11 May, 2016

1 commit

  • This is an initial implementation of a netdev driver for GTP datapath
    (GTP-U) v0 and v1, according to the GSM TS 09.60 and 3GPP TS 29.060
    standards. This tunneling protocol is used to prevent subscribers from
    accessing mobile carrier core network infrastructure.

    This implementation requires a GGSN userspace daemon that implements the
    signaling protocol (GTP-C), such as OpenGGSN [1]. This userspace daemon
    updates the PDP context database that represents active subscriber
    sessions through a genetlink interface.

    For more context on this tunneling protocol, you can check the slides
    that were presented during the NetDev 1.1 [2].

    Only IPv4 is supported at this time.

    [1] http://git.osmocom.org/openggsn/
    [2] http://www.netdevconf.org/1.1/proceedings/slides/schultz-welte-osmocom-gtp.pdf

    Signed-off-by: Pablo Neira Ayuso
    Signed-off-by: David S. Miller

    Pablo Neira
     

26 Apr, 2016

1 commit


18 Apr, 2016

1 commit

  • The new MACsec driver uses the AES crypto algorithm, but can be configured
    even if CONFIG_CRYPTO is disabled, leading to a build error:

    warning: (MAC80211 && MACSEC) selects CRYPTO_GCM which has unmet direct dependencies (CRYPTO)
    warning: (BT && CEPH_LIB && INET && MAC802154 && MAC80211 && BLK_DEV_RBD && MACSEC && AIRO_CS && LIBIPW && HOSTAP && USB_WUSB && RTLLIB_CRYPTO_CCMP && FS_ENCRYPTION && EXT4_ENCRYPTION && CEPH_FS && BIG_KEYS && ENCRYPTED_KEYS) selects CRYPTO_AES which has unmet direct dependencies (CRYPTO)
    crypto/built-in.o: In function `gcm_enc_copy_hash':
    aes_generic.c:(.text+0x2b8): undefined reference to `crypto_xor'
    aes_generic.c:(.text+0x2dc): undefined reference to `scatterwalk_map_and_copy'

    This adds an explicit 'select CRYPTO' statement the way that other
    drivers handle it.

    Signed-off-by: Arnd Bergmann
    Fixes: c09440f7dcb3 ("macsec: introduce IEEE 802.1AE driver")
    Signed-off-by: David S. Miller

    Arnd Bergmann
     

14 Mar, 2016

1 commit

  • This is an implementation of MACsec/IEEE 802.1AE. This driver
    provides authentication and encryption of traffic in a LAN, typically
    with GCM-AES-128, and optional replay protection.

    http://standards.ieee.org/getieee802/download/802.1AE-2006.pdf

    Signed-off-by: Sabrina Dubroca
    Reviewed-by: Hannes Frederic Sowa
    Signed-off-by: David S. Miller

    Sabrina Dubroca
     

13 Oct, 2015

1 commit


30 Sep, 2015

1 commit


28 Aug, 2015

1 commit

  • geneve_core module handles send and receive functionality.
    This way OVS could use the Geneve API. Now with use of
    tunnel meatadata mode OVS can directly use Geneve netdevice.
    So there is no need for separate module for Geneve. Following
    patch consolidates Geneve protocol processing in single module.

    Signed-off-by: Pravin B Shelar
    Reviewed-by: Jesse Gross
    Acked-by: John W. Linville
    Signed-off-by: David S. Miller

    Pravin B Shelar
     

25 Aug, 2015

1 commit

  • This patch adds the basic code of FUJITSU Extended Socket
    Network Device driver.

    When "PNP0C02" is found in ACPI DSDT, it evaluates "_STR"
    to check if "PNP0C02" is for Extended Socket device driver
    and retrieves ACPI resource information. Then creates
    platform_device.

    Signed-off-by: Taku Izumi
    Signed-off-by: David S. Miller

    Taku Izumi
     

21 Aug, 2015

1 commit

  • Instead of using the out-of-line EWMA calculation, use DECLARE_EWMA()
    to create static inlines. On x86/64 this results in no change in code
    size for me, but reduces the struct receive_queue size by the two
    unsigned long values that store the parameters.

    Signed-off-by: Johannes Berg
    Signed-off-by: David S. Miller

    Johannes Berg
     

14 Aug, 2015

1 commit

  • This driver borrows heavily from IPvlan and teaming drivers.

    Routing domains (VRF-lite) are created by instantiating a VRF master
    device with an associated table and enslaving all routed interfaces that
    participate in the domain. As part of the enslavement, all connected
    routes for the enslaved devices are moved to the table associated with
    the VRF device. Outgoing sockets must bind to the VRF device to function.

    Standard FIB rules bind the VRF device to tables and regular fib rule
    processing is followed. Routed traffic through the box, is forwarded by
    using the VRF device as the IIF and following the IIF rule to a table
    that is mated with the VRF.

    Example:

    Create vrf 1:
    ip link add vrf1 type vrf table 5
    ip rule add iif vrf1 table 5
    ip rule add oif vrf1 table 5
    ip route add table 5 prohibit default
    ip link set vrf1 up

    Add interface to vrf 1:
    ip link set eth1 master vrf1

    Signed-off-by: Shrijeet Mukherjee
    Signed-off-by: David Ahern
    Signed-off-by: David S. Miller

    David Ahern
     

05 Jul, 2015

1 commit

  • Pull NTB updates from Jon Mason:
    "This includes a pretty significant reworking of the NTB core code, but
    has already produced some significant performance improvements.

    An abstraction layer was added to allow the hardware and clients to be
    easily added. This required rewriting the NTB transport layer for
    this abstraction layer. This modification will allow future "high
    performance" NTB clients.

    In addition to this change, a number of performance modifications were
    added. These changes include NUMA enablement, using CPU memcpy
    instead of asyncdma, and modification of NTB layer MTU size"

    * tag 'ntb-4.2' of git://github.com/jonmason/ntb: (22 commits)
    NTB: Add split BAR output for debugfs stats
    NTB: Change WARN_ON_ONCE to pr_warn_once on unsafe
    NTB: Print driver name and version in module init
    NTB: Increase transport MTU to 64k from 16k
    NTB: Rename Intel code names to platform names
    NTB: Default to CPU memcpy for performance
    NTB: Improve performance with write combining
    NTB: Use NUMA memory in Intel driver
    NTB: Use NUMA memory and DMA chan in transport
    NTB: Rate limit ntb_qp_link_work
    NTB: Add tool test client
    NTB: Add ping pong test client
    NTB: Add parameters for Intel SNB B2B addresses
    NTB: Reset transport QP link stats on down
    NTB: Do not advance transport RX on link down
    NTB: Differentiate transport link down messages
    NTB: Check the device ID to set errata flags
    NTB: Enable link for Intel root port mode in probe
    NTB: Read peer info from local SPAD in transport
    NTB: Split ntb_hw_intel and ntb_transport drivers
    ...

    Linus Torvalds
     

04 Jul, 2015

1 commit

  • Pull virtio/vhost cross endian support from Michael Tsirkin:
    "I have just queued some more bugfix patches today but none fix
    regressions and none are related to these ones, so it looks like a
    good time for a merge for -rc1.

    The motivation for this is support for legacy BE guests on the new LE
    hosts. There are two redeeming properties that made me merge this:

    - It's a trivial amount of code: since we wrap host/guest accesses
    anyway, almost all of it is well hidden from drivers.

    - Sane platforms would never set flags like VHOST_CROSS_ENDIAN_LEGACY,
    and when it's clear, there's zero overhead (as some point it was
    tested by compiling with and without the patches, got the same
    stripped binary).

    Maybe we could create a Kconfig symbol to enforce the second point:
    prevent people from enabling it eg on x86. I will look into this"

    * tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost:
    virtio-pci: alloc only resources actually used.
    macvtap/tun: cross-endian support for little-endian hosts
    vhost: cross-endian support for legacy devices
    virtio: add explicit big-endian support to memory accessors
    vhost: introduce vhost_is_little_endian() helper
    vringh: introduce vringh_is_little_endian() helper
    macvtap: introduce macvtap_is_little_endian() helper
    tun: add tun_is_little_endian() helper
    virtio: introduce virtio_is_little_endian() helper

    Linus Torvalds
     

02 Jul, 2015

1 commit

  • This patch only moves files to their new locations, before applying the
    next two patches adding the NTB Abstraction layer. Splitting this patch
    from the next is intended make distinct which code is changed only due
    to moving the files, versus which are substantial code changes in adding
    the NTB Abstraction layer.

    Signed-off-by: Allen Hubbe
    Signed-off-by: Jon Mason

    Allen Hubbe
     

01 Jun, 2015

1 commit

  • The VNET_LE flag was introduced to fix accesses to virtio 1.0 headers
    that are always little-endian. It can also be used to handle the special
    case of a legacy little-endian device implemented by a big-endian host.

    Let's add a flag and ioctls for big-endian devices as well. If both flags
    are set, little-endian wins.

    Since this is isn't a common usecase, the feature is controlled by a kernel
    config option (not set by default).

    Both macvtap and tun are covered by this patch since they share the same
    API with userland.

    Signed-off-by: Greg Kurz

    Signed-off-by: Michael S. Tsirkin
    Reviewed-by: David Gibson

    Greg Kurz
     

14 May, 2015

1 commit


21 Feb, 2015

1 commit


07 Jan, 2015

1 commit

  • SRCU is not necessary to be compiled by default in all cases. For tinification
    efforts not compiling SRCU unless necessary is desirable.

    The current patch tries to make compiling SRCU optional by introducing a new
    Kconfig option CONFIG_SRCU which is selected when any of the components making
    use of SRCU are selected.

    If we do not select CONFIG_SRCU, srcu.o will not be compiled at all.

    text data bss dec hex filename
    2007 0 0 2007 7d7 kernel/rcu/srcu.o

    Size of arch/powerpc/boot/zImage changes from

    text data bss dec hex filename
    831552 64180 23944 919676 e087c arch/powerpc/boot/zImage : before
    829504 64180 23952 917636 e0084 arch/powerpc/boot/zImage : after

    so the savings are about ~2000 bytes.

    Signed-off-by: Pranith Kumar
    CC: Paul E. McKenney
    CC: Josh Triplett
    CC: Lai Jiangshan
    Signed-off-by: Paul E. McKenney
    [ paulmck: resolve conflict due to removal of arch/ia64/kvm/Kconfig. ]

    Pranith Kumar
     

30 Nov, 2014

1 commit


25 Nov, 2014

1 commit

  • This driver is very similar to the macvlan driver except that it
    uses L3 on the frame to determine the logical interface while
    functioning as packet dispatcher. It inherits L2 of the master
    device hence the packets on wire will have the same L2 for all
    the packets originating from all virtual devices off of the same
    master device.

    This driver was developed keeping the namespace use-case in
    mind. Hence most of the examples given here take that as the
    base setup where main-device belongs to the default-ns and
    virtual devices are assigned to the additional namespaces.

    The device operates in two different modes and the difference
    in these two modes in primarily in the TX side.

    (a) L2 mode : In this mode, the device behaves as a L2 device.
    TX processing upto L2 happens on the stack of the virtual device
    associated with (namespace). Packets are switched after that
    into the main device (default-ns) and queued for xmit.

    RX processing is simple and all multicast, broadcast (if
    applicable), and unicast belonging to the address(es) are
    delivered to the virtual devices.

    (b) L3 mode : In this mode, the device behaves like a L3 device.
    TX processing upto L3 happens on the stack of the virtual device
    associated with (namespace). Packets are switched to the
    main-device (default-ns) for the L2 processing. Hence the routing
    table of the default-ns will be used in this mode.

    RX processins is somewhat similar to the L2 mode except that in
    this mode only Unicast packets are delivered to the virtual device
    while main-dev will handle all other packets.

    The devices can be added using the "ip" command from the iproute2
    package -

    ip link add link type ipvlan mode [ l2 | l3 ]

    Signed-off-by: Mahesh Bandewar
    Cc: Eric Dumazet
    Cc: Maciej Żenczykowski
    Cc: Laurent Chavey
    Cc: Tim Hockin
    Cc: Brandon Philips
    Cc: Pavel Emelianov
    Signed-off-by: David S. Miller

    Mahesh Bandewar
     

31 Oct, 2014

1 commit

  • These drivers now call ipv6_proxy_select_ident(), which is defined
    only if CONFIG_INET is enabled. However, they have really depended
    on CONFIG_INET for as long as they have allowed sending GSO packets
    from userland.

    Reported-by: kbuild test robot
    Signed-off-by: Ben Hutchings
    Fixes: f43798c27684 ("tun: Allow GSO using virtio_net_hdr")
    Fixes: b9fb9ee07e67 ("macvtap: add GSO/csum offload support")
    Fixes: 5188cd44c55d ("drivers/net, ipv6: Select IPv6 fragment idents for virtio UFO packets")
    Signed-off-by: David S. Miller

    Ben Hutchings
     

07 Oct, 2014

1 commit

  • Fix a openvswitch compilation error when CONFIG_INET is not set:

    =====================================================
    In file included from include/net/geneve.h:4:0,
    from net/openvswitch/flow_netlink.c:45:
    include/net/udp_tunnel.h: In function 'udp_tunnel_handle_offloads':
    >> include/net/udp_tunnel.h:100:2: error: implicit declaration of function 'iptunnel_handle_offloads' [-Werror=implicit-function-declaration]
    >> return iptunnel_handle_offloads(skb, udp_csum, type);
    >> ^
    >> >> include/net/udp_tunnel.h:100:2: warning: return makes pointer from integer without a cast
    >> >> cc1: some warnings being treated as errors

    =====================================================

    Reported-by: kbuild test robot
    Signed-off-by: Andy Zhou
    Signed-off-by: David S. Miller

    Andy Zhou