1. 31 Dec, 2021 7 commits
  2. 30 Dec, 2021 30 commits
  3. 29 Dec, 2021 3 commits
    • Jakub Kicinski's avatar
      Merge tag 'for-net-next-2021-12-29' of... · e2dfb94f
      Jakub Kicinski authored
      Merge tag 'for-net-next-2021-12-29' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next
      
      Luiz Augusto von Dentz says:
      
      ====================
      bluetooth-next pull request for net-next:
      
       - Add support for Foxconn MT7922A
       - Add support for Realtek RTL8852AE
       - Rework HCI event handling to use skb_pull_data
      
      * tag 'for-net-next-2021-12-29' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next: (62 commits)
        Bluetooth: MGMT: Fix spelling mistake "simultanous" -> "simultaneous"
        Bluetooth: vhci: Set HCI_QUIRK_VALID_LE_STATES
        Bluetooth: MGMT: Fix LE simultaneous roles UUID if not supported
        Bluetooth: hci_sync: Add check simultaneous roles support
        Bluetooth: hci_sync: Wait for proper events when connecting LE
        Bluetooth: hci_sync: Add support for waiting specific LE subevents
        Bluetooth: hci_sync: Add hci_le_create_conn_sync
        Bluetooth: hci_event: Use skb_pull_data when processing inquiry results
        Bluetooth: hci_sync: Push sync command cancellation to workqueue
        Bluetooth: hci_qca: Stop IBS timer during BT OFF
        Bluetooth: btusb: Add support for Foxconn MT7922A
        Bluetooth: btintel: Add missing quirks and msft ext for legacy bootloader
        Bluetooth: btusb: Add two more Bluetooth parts for WCN6855
        Bluetooth: L2CAP: Fix using wrong mode
        Bluetooth: hci_sync: Fix not always pausing advertising when necessary
        Bluetooth: mgmt: Make use of mgmt_send_event_skb in MGMT_EV_DEVICE_CONNECTED
        Bluetooth: mgmt: Make use of mgmt_send_event_skb in MGMT_EV_DEVICE_FOUND
        Bluetooth: mgmt: Introduce mgmt_alloc_skb and mgmt_send_event_skb
        Bluetooth: btusb: Return error code when getting patch status failed
        Bluetooth: btusb: Handle download_firmware failure cases
        ...
      ====================
      
      Link: https://lore.kernel.org/r/20211229211258.2290966-1-luiz.dentz@gmail.comSigned-off-by: default avatarJakub Kicinski <kuba@kernel.org>
      e2dfb94f
    • Jakub Kicinski's avatar
      Merge branch 'net-bridge-mcast-add-and-enforce-query-interval-minimum' · f7397cd2
      Jakub Kicinski authored
      Nikolay Aleksandrov says:
      
      ====================
      net: bridge: mcast: add and enforce query interval minimum
      
      This set adds and enforces 1 second minimum value for bridge multicast
      query and startup query intervals in order to avoid rearming the timers
      too often which could lock and crash the host. I doubt anyone is using
      such low values or anything lower than 1 second, so it seems like a good
      minimum. In order to be compatible if the value is lower then it is
      overwritten and a log message is emitted, since we can't return an error
      at this point.
      
      Eric, I looked for the syzbot reports in its dashboard but couldn't find
      them so I've added you as the reporter.
      
      I've prepared a global bridge igmp rate limiting patch but wasn't
      sure if it's ok for -net. It adds a static limit of 32k packets per
      second, I plan to send it for net-next with added drop counters for
      each bridge so it can be easily debugged.
      
      Original report can be seen at:
      https://lore.kernel.org/netdev/e8b9ce41-57b9-b6e2-a46a-ff9c791cf0ba@gmail.com/
      ====================
      
      Link: https://lore.kernel.org/r/20211227172116.320768-1-nikolay@nvidia.comSigned-off-by: default avatarJakub Kicinski <kuba@kernel.org>
      f7397cd2
    • Nikolay Aleksandrov's avatar
      net: bridge: mcast: add and enforce startup query interval minimum · f83a112b
      Nikolay Aleksandrov authored
      As reported[1] if startup query interval is set too low in combination with
      large number of startup queries and we have multiple bridges or even a
      single bridge with multiple querier vlans configured we can crash the
      machine. Add a 1 second minimum which must be enforced by overwriting the
      value if set lower (i.e. without returning an error) to avoid breaking
      user-space. If that happens a log message is emitted to let the admin know
      that the startup interval has been set to the minimum. It doesn't make
      sense to make the startup interval lower than the normal query interval
      so use the same value of 1 second. The issue has been present since these
      intervals could be user-controlled.
      
      [1] https://lore.kernel.org/netdev/e8b9ce41-57b9-b6e2-a46a-ff9c791cf0ba@gmail.com/
      
      Fixes: d902eee4 ("bridge: Add multicast count/interval sysfs entries")
      Reported-by: default avatarEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: default avatarNikolay Aleksandrov <nikolay@nvidia.com>
      Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
      f83a112b