1. 18 Feb, 2022 3 commits
  2. 16 Feb, 2022 25 commits
  3. 14 Feb, 2022 7 commits
  4. 11 Feb, 2022 5 commits
    • David S. Miller's avatar
      Merge tag 'wireless-next-2022-02-11' of... · b96a7925
      David S. Miller authored
      Merge tag 'wireless-next-2022-02-11' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next
      
      wireless-next patches for v5.18
      
      First set of patches for v5.18, with both wireless and stack patches.
      rtw89 now has AP mode support and wcn36xx has survey support. But
      otherwise pretty normal.
      
      Major changes:
      
      ath11k
      
      * add LDPC FEC type in 802.11 radiotap header
      
      * enable RX PPDU stats in monitor co-exist mode
      
      wcn36xx
      
      * implement survey reporting
      
      brcmfmac
      
      * add CYW43570 PCIE device
      
      rtw88
      
      * rtw8821c: enable RFE 6 devices
      
      rtw89
      
      * AP mode support
      
      mt76
      
      * mt7916 support
      
      * background radar detection support
      b96a7925
    • David S. Miller's avatar
      Merge branch 'ipv6-loopback' · c002496b
      David S. Miller authored
      Eric Dumazet says:
      
      ====================
      ipv6: remove addrconf reliance on loopback
      
      Second patch in this series removes IPv6 requirement about the netns
      loopback device being the last device being dismantled.
      
      This was needed because rt6_uncached_list_flush_dev()
      and ip6_dst_ifdown() had to switch dst dev to a known
      device (loopback).
      
      Instead of loopback, we can use the (hidden) blackhole_netdev
      which is also always there.
      
      This will allow future simplfications of netdev_run_to()
      and other parts of the stack like default_device_exit_batch().
      
      Last two patches are optimizations for both IP families.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c002496b
    • Eric Dumazet's avatar
      ipv4: add (struct uncached_list)->quarantine list · 29e5375d
      Eric Dumazet authored
      This is an optimization to keep the per-cpu lists as short as possible:
      
      Whenever rt_flush_dev() changes one rtable dst.dev
      matching the disappearing device, it can can transfer the object
      to a quarantine list, waiting for a final rt_del_uncached_list().
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      29e5375d
    • Eric Dumazet's avatar
      ipv6: add (struct uncached_list)->quarantine list · ba55ef81
      Eric Dumazet authored
      This is an optimization to keep the per-cpu lists as short as possible:
      
      Whenever rt6_uncached_list_flush_dev() changes one rt6_info
      matching the disappearing device, it can can transfer the object
      to a quarantine list, waiting for a final rt6_uncached_list_del().
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ba55ef81
    • Eric Dumazet's avatar
      ipv6: give an IPv6 dev to blackhole_netdev · e5f80fcf
      Eric Dumazet authored
      IPv6 addrconf notifiers wants the loopback device to
      be the last device being dismantled at netns deletion.
      
      This caused many limitations and work arounds.
      
      Back in linux-5.3, Mahesh added a per host blackhole_netdev
      that can be used whenever we need to make sure objects no longer
      refer to a disappearing device.
      
      If we attach to blackhole_netdev an ip6_ptr (allocate an idev),
      then we can use this special device (which is never freed)
      in place of the loopback_dev (which can be freed).
      
      This will permit improvements in netdev_run_todo() and other parts
      of the stack where had steps to make sure loopback_dev was
      the last device to disappear.
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Cc: Mahesh Bandewar <maheshb@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e5f80fcf