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: pull request: bluetooth 2024-04-10
Date: Wed, 10 Apr 2024 15:16:10 -0400 [thread overview]
Message-ID: <20240410191610.4156653-1-luiz.dentz@gmail.com> (raw)
The following changes since commit 19fa4f2a85d777a8052e869c1b892a2f7556569d:
r8169: fix LED-related deadlock on module removal (2024-04-10 10:44:29 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2024-04-10
for you to fetch changes up to 600b0bbe73d3a9a264694da0e4c2c0800309141e:
Bluetooth: l2cap: Don't double set the HCI_CONN_MGMT_CONNECTED bit (2024-04-10 15:10:16 -0400)
----------------------------------------------------------------
bluetooth pull request for net:
- L2CAP: Don't double set the HCI_CONN_MGMT_CONNECTED bit
- Fix memory leak in hci_req_sync_complete
- hci_sync: Fix using the same interval and window for Coded PHY
- Fix not validating setsockopt user input
----------------------------------------------------------------
Archie Pusaka (1):
Bluetooth: l2cap: Don't double set the HCI_CONN_MGMT_CONNECTED bit
Dmitry Antipov (1):
Bluetooth: Fix memory leak in hci_req_sync_complete()
Luiz Augusto von Dentz (7):
Bluetooth: ISO: Don't reject BT_ISO_QOS if parameters are unset
Bluetooth: hci_sync: Fix using the same interval and window for Coded PHY
Bluetooth: SCO: Fix not validating setsockopt user input
Bluetooth: RFCOMM: Fix not validating setsockopt user input
Bluetooth: L2CAP: Fix not validating setsockopt user input
Bluetooth: ISO: Fix not validating setsockopt user input
Bluetooth: hci_sock: Fix not validating setsockopt user input
include/net/bluetooth/bluetooth.h | 9 +++++++
net/bluetooth/hci_request.c | 4 ++-
net/bluetooth/hci_sock.c | 21 ++++++----------
net/bluetooth/hci_sync.c | 6 ++---
net/bluetooth/iso.c | 46 +++++++++++++++-------------------
net/bluetooth/l2cap_core.c | 3 +--
net/bluetooth/l2cap_sock.c | 52 +++++++++++++++------------------------
net/bluetooth/rfcomm/sock.c | 14 ++++-------
net/bluetooth/sco.c | 23 ++++++++---------
9 files changed, 79 insertions(+), 99 deletions(-)
next reply other threads:[~2024-04-10 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 19:16 Luiz Augusto von Dentz [this message]
2024-04-12 1:56 ` pull request: bluetooth 2024-04-10 Jakub Kicinski
2024-04-25 16:22 ` patchwork-bot+bluetooth
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=20240410191610.4156653-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).