Netdev List
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] bluetooth 2026-10-12
Date: Mon, 12 Oct 2026 17:07:58 -0400	[thread overview]
Message-ID: <20261012210758.275556-1-luiz.dentz@gmail.com> (raw)

The following changes since commit e32d80293a0e1a160d5e5101daa8c82148c07510:

  Bluetooth: ISO: Serialize concurrent connect calls (2026-10-05 13:10:47 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2026-10-12

for you to fetch changes up to 23ad91f6a21a830b67f5eee790caa0053bd6537d:

  Bluetooth: MSFT: Serialize handle map cleanup with event processing (2026-10-12 16:27:16 -0400)

----------------------------------------------------------------
bluetooth pull request for net:

Core:

 - hci_core: Keep RCU protection through LTK filtering
 - hci_sync: Serialize devcoredump reset during device open
 - hci_sync: Protect IRK identity reads with RCU
 - hci_sync: fix mesh adv timeout units
 - hci_debugfs: Pin module for debugfs file operations
 - L2CAP: Hold the listener while notifying child teardown
 - ISO: Hold the listener during disconnect notification
 - MGMT: Reject quality report requests during unregister
 - MGMT: Fix advertising instances with Global Advertising
 - MGMT: Fix pending state of instances added without HCI traffic
 - MGMT: Fix leaking instance on Add Extended Advertising Parameters
 - MGMT: Allow connection rate request as peripheral
 - selftest: Pin module for selftest debugfs file operations
 - 6lowpan: Pin module for 6lowpan_control debugfs file
 - 6LoWPAN: Use RCU-safe device list removal
 - 6lowpan: Drain RCU readers on registration failure
 - msft: Lock failed probe cleanup against feature readers
 - MSFT: Serialize handle map cleanup with event processing
 - Add missing newline to bt_dev_{err,warn}_ratelimited()
 - Fix tracking of instances sharing handle 0x00

Drivers:

 - btintel: Zero version data before parsing TLVs
 - btmtk: fix skb double free on ISO padding failure
 - hci_vhci: Pin module for debugfs file operations

----------------------------------------------------------------
Bui Viet Dung (4):
      Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file
      Bluetooth: hci_debugfs: Pin module for debugfs file operations
      Bluetooth: hci_vhci: Pin module for debugfs file operations
      Bluetooth: selftest: Pin module for selftest debugfs file operations

Cen Zhang (10):
      Bluetooth: 6LoWPAN: Use RCU-safe device list removal
      Bluetooth: hci_core: Keep RCU protection through LTK filtering
      Bluetooth: hci_sync: Serialize devcoredump reset during device open
      Bluetooth: ISO: Hold the listener during disconnect notification
      Bluetooth: MGMT: Reject quality report requests during unregister
      Bluetooth: msft: Lock failed probe cleanup against feature readers
      Bluetooth: 6lowpan: Drain RCU readers on registration failure
      Bluetooth: hci_sync: Protect IRK identity reads with RCU
      Bluetooth: L2CAP: Hold the listener while notifying child teardown
      Bluetooth: MSFT: Serialize handle map cleanup with event processing

Eric Dumazet (1):
      Bluetooth: btmtk: fix skb double free on ISO padding failure

Hitalo Souza (1):
      Bluetooth: Add missing newline to bt_dev_{err,warn}_ratelimited()

Kiran K (1):
      Bluetooth: btintel: Zero version data before parsing TLVs

Luiz Augusto von Dentz (5):
      Bluetooth: MGMT: Fix advertising instances with Global Advertising
      Bluetooth: HCI: Fix tracking of instances sharing handle 0x00
      Bluetooth: MGMT: Fix pending state of instances added without HCI traffic
      Bluetooth: MGMT: Fix leaking instance on Add Extended Advertising Parameters
      Bluetooth: MGMT: Allow connection rate request as peripheral

Pauli Virtanen (1):
      Bluetooth: hci_sync: fix mesh adv timeout units

 drivers/bluetooth/btintel.c       |   1 +
 drivers/bluetooth/btmtk.c         |   8 +--
 drivers/bluetooth/hci_vhci.c      |   4 ++
 drivers/bluetooth/virtio_bt.c     |   4 +-
 include/net/bluetooth/bluetooth.h |   4 +-
 include/net/bluetooth/hci_sync.h  |   1 +
 net/bluetooth/6lowpan.c           |   4 +-
 net/bluetooth/hci_core.c          |   4 +-
 net/bluetooth/hci_debugfs.c       |   9 +++
 net/bluetooth/hci_event.c         |  58 ++++++++++++++----
 net/bluetooth/hci_sync.c          |  53 +++++++++++++++--
 net/bluetooth/iso.c               |   3 +
 net/bluetooth/l2cap_sock.c        |   6 ++
 net/bluetooth/mgmt.c              | 122 ++++++++++++++++++++++++++++++++------
 net/bluetooth/msft.c              |   6 ++
 net/bluetooth/selftest.c          |   1 +
 net/bluetooth/smp.c               |   1 +
 17 files changed, 241 insertions(+), 48 deletions(-)

             reply	other threads:[~2026-10-12 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 21:07 Luiz Augusto von Dentz [this message]
2026-10-13  9:25 ` [GIT PULL] bluetooth 2026-10-12 Paolo Abeni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261012210758.275556-1-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox