1. 01 Feb, 2017 9 commits
    • Niklas Söderlund's avatar
      sh_eth: align usage of sh_eth_modify() with rest of driver · 5e2ed132
      Niklas Söderlund authored
      To be consistent with the rest of the driver when setting bits using
      sh_eth_modify() the same bit should also be cleared. This have no
      functional change and should have been done from the start.
      Signed-off-by: default avatarNiklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
      Suggested-by: default avatarSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Acked-by: default avatarSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      5e2ed132
    • David S. Miller's avatar
      Merge tag 'wireless-drivers-next-for-davem-2017-02-01' of... · 889711a0
      David S. Miller authored
      Merge tag 'wireless-drivers-next-for-davem-2017-02-01' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
      
      Kalle Valo says:
      
      ====================
      wireless-drivers-next patches for 4.11
      
      It's nice to see rt2x00 development has becoming active, for example
      adding support for a new chip version. Also wcn36xx has been converted
      to use the recently merged QCOM_SMD subsystem. Otherwise new features
      and fixes it lots of drivers.
      
      Major changes:
      
      iwlwifi
      
      * some more work in preparation for A000 family support
      * add support for radiotap timestamps
      * some work on our firmware debugging capabilities
      
      wcn36xx
      
      * convert to a proper QCOM_SMD driver (from the platform_driver interface)
      
      ath10k
      
      * VHT160 support
      * dump Copy Engine registers during firmware crash
      * search board file extension from SMBIOS
      
      wil6210
      
      * add disable_ap_sme module parameter
      
      rt2x00
      
      * support RT3352 with external PA
      * support for RT3352 with 20MHz crystal
      * add support for RT5350 WiSoC
      
      brcmfmac
      
      * add support for BCM43455 sdio device
      
      rtl8xxxu
      
      * add support for D-Link DWA-131 rev E1, TP-Link TL-WN822N v4 and others
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      889711a0
    • Dan Carpenter's avatar
      ethernet: aquantia: fix dma_mapping_error test · ff1176f6
      Dan Carpenter authored
      dma_mapping_error() returns 1 if there is an error and 0 if not.
      
      Fixes: 018423e9 ("net: ethernet: aquantia: Add ring support code")
      Signed-off-by: default avatarDan Carpenter <dan.carpenter@oracle.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ff1176f6
    • Satanand Burla's avatar
      liquidio: fix for iq and droq cnts going negative · cdb478e5
      Satanand Burla authored
      Flush the mmio writes before releasing spin locks.
      if the maintained counts get too high > 2M force
      writeback of the counts to clear them
      Signed-off-by: default avatarSatanand Burla <satananda.burla@cavium.com>
      Signed-off-by: default avatarFelix Manlunas <felix.manlunas@cavium.com>
      Signed-off-by: default avatarRaghu Vatsavayi <raghu.vatsavayi@cavium.com>
      Signed-off-by: default avatarDerek Chickles <derek.chickles@cavium.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      cdb478e5
    • David Ahern's avatar
      net: ipv6: add NLM_F_APPEND in notifications when applicable · 1f5e29ce
      David Ahern authored
      IPv6 does not set the NLM_F_APPEND flag in notifications to signal that
      a NEWROUTE is an append versus a new route or a replaced one. Add the
      flag if the request has it.
      Signed-off-by: default avatarDavid Ahern <dsa@cumulusnetworks.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      1f5e29ce
    • Grygorii Strashko's avatar
      net: ethernet: ti: cpsw: fix NULL pointer dereference in switch mode · f6961862
      Grygorii Strashko authored
      In switch mode on struct cpsw_slave->ndev field will be initialized with
      proper value only for the one cpsw slave port, as result
      cpsw_get_usage_count() will generate "Unable to handle kernel NULL pointer
      dereference" exception when first ethernet interface is opening
      cpsw_ndo_open(). This issue causes boot regression on AM335x EVM and
      reproducible on am57xx-evm (switch mode).
      Fix it by adding additional check for !cpsw->slaves[i].ndev in
      cpsw_get_usage_count().
      
      Cc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
      Fixes: 03fd01ad ("net: ethernet: ti: cpsw: don't duplicate ndev_running")
      Signed-off-by: default avatarGrygorii Strashko <grygorii.strashko@ti.com>
      Reviewed-by: default avatarIvan Khoronzhuk <ivan.khoronzhuk@linaro.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      f6961862
    • Eric Dumazet's avatar
      net: reduce skb_warn_bad_offload() noise · b2504a5d
      Eric Dumazet authored
      Dmitry reported warnings occurring in __skb_gso_segment() [1]
      
      All SKB_GSO_DODGY producers can allow user space to feed
      packets that trigger the current check.
      
      We could prevent them from doing so, rejecting packets, but
      this might add regressions to existing programs.
      
      It turns out our SKB_GSO_DODGY handlers properly set up checksum
      information that is needed anyway when packets needs to be segmented.
      
      By checking again skb_needs_check() after skb_mac_gso_segment(),
      we should remove these pesky warnings, at a very minor cost.
      
      With help from Willem de Bruijn
      
      [1]
      WARNING: CPU: 1 PID: 6768 at net/core/dev.c:2439 skb_warn_bad_offload+0x2af/0x390 net/core/dev.c:2434
      lo: caps=(0x000000a2803b7c69, 0x0000000000000000) len=138 data_len=0 gso_size=15883 gso_type=4 ip_summed=0
      Kernel panic - not syncing: panic_on_warn set ...
      
      CPU: 1 PID: 6768 Comm: syz-executor1 Not tainted 4.9.0 #5
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
       ffff8801c063ecd8 ffffffff82346bdf ffffffff00000001 1ffff100380c7d2e
       ffffed00380c7d26 0000000041b58ab3 ffffffff84b37e38 ffffffff823468f1
       ffffffff84820740 ffffffff84f289c0 dffffc0000000000 ffff8801c063ee20
      Call Trace:
       [<ffffffff82346bdf>] __dump_stack lib/dump_stack.c:15 [inline]
       [<ffffffff82346bdf>] dump_stack+0x2ee/0x3ef lib/dump_stack.c:51
       [<ffffffff81827e34>] panic+0x1fb/0x412 kernel/panic.c:179
       [<ffffffff8141f704>] __warn+0x1c4/0x1e0 kernel/panic.c:542
       [<ffffffff8141f7e5>] warn_slowpath_fmt+0xc5/0x100 kernel/panic.c:565
       [<ffffffff8356cbaf>] skb_warn_bad_offload+0x2af/0x390 net/core/dev.c:2434
       [<ffffffff83585cd2>] __skb_gso_segment+0x482/0x780 net/core/dev.c:2706
       [<ffffffff83586f19>] skb_gso_segment include/linux/netdevice.h:3985 [inline]
       [<ffffffff83586f19>] validate_xmit_skb+0x5c9/0xc20 net/core/dev.c:2969
       [<ffffffff835892bb>] __dev_queue_xmit+0xe6b/0x1e70 net/core/dev.c:3383
       [<ffffffff8358a2d7>] dev_queue_xmit+0x17/0x20 net/core/dev.c:3424
       [<ffffffff83ad161d>] packet_snd net/packet/af_packet.c:2930 [inline]
       [<ffffffff83ad161d>] packet_sendmsg+0x32ed/0x4d30 net/packet/af_packet.c:2955
       [<ffffffff834f0aaa>] sock_sendmsg_nosec net/socket.c:621 [inline]
       [<ffffffff834f0aaa>] sock_sendmsg+0xca/0x110 net/socket.c:631
       [<ffffffff834f329a>] ___sys_sendmsg+0x8fa/0x9f0 net/socket.c:1954
       [<ffffffff834f5e58>] __sys_sendmsg+0x138/0x300 net/socket.c:1988
       [<ffffffff834f604d>] SYSC_sendmsg net/socket.c:1999 [inline]
       [<ffffffff834f604d>] SyS_sendmsg+0x2d/0x50 net/socket.c:1995
       [<ffffffff84371941>] entry_SYSCALL_64_fastpath+0x1f/0xc2
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Reported-by: default avatarDmitry Vyukov  <dvyukov@google.com>
      Cc: Willem de Bruijn <willemb@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b2504a5d
    • Theuns Verwoerd's avatar
      rtnetlink: Handle IFLA_MASTER parameter when processing rtnl_newlink · 160ca014
      Theuns Verwoerd authored
      Allow a master interface to be specified as one of the parameters when
      creating a new interface via rtnl_newlink.  Previously this would
      require invoking interface creation, waiting for it to complete, and
      then separately binding that new interface to a master.
      
      In particular, this is used when creating a macvlan child interface for
      VRRP in a VRF configuration, allowing the interface creator to specify
      directly what master interface should be inherited by the child,
      without having to deal with asynchronous complications and potential
      race conditions.
      Signed-off-by: default avatarTheuns Verwoerd <theuns.verwoerd@alliedtelesis.co.nz>
      Acked-by: default avatarDavid Ahern <dsa@cumulusnetworks.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      160ca014
    • David S. Miller's avatar
      Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next · 04cdf13e
      David S. Miller authored
      Steffen Klassert says:
      
      ====================
      pull request (net-next): ipsec-next 2017-02-01
      
      1) Some typo fixes, from Alexander Alemayhu.
      
      2) Don't acquire state lock in get_mtu functions.
         The only rece against a dead state does not matter.
         From Florian Westphal.
      
      3) Remove xfrm4_state_fini, it is unused for more than
         10 years. From Florian Westphal.
      
      4) Various rcu usage improvements. From Florian Westphal.
      
      5) Properly handle crypto arrors in ah4/ah6.
         From Gilad Ben-Yossef.
      
      6) Try to avoid skb linearization in esp4 and esp6.
      
      7) The esp trailer is now set up in different places,
         add a helper for this.
      
      8) With the upcomming usage of gro_cells in IPsec,
         a gro merged skb can have a secpath. Drop it
         before freeing or reusing the skb.
      
      9) Add a xfrm dummy network device for napi. With
         this we can use gro_cells from within xfrm,
         it allows IPsec GRO without impact on the generic
         networking code.
      
      Please pull or let me know if there are problems.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      04cdf13e
  2. 31 Jan, 2017 23 commits
  3. 30 Jan, 2017 8 commits