Bug fixes for RFCOMM and L2CAP
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Bluetooth: Clear RFCOMM session timer when disconnecting last channelnet/ | +1 | 3 replies | |
| 2/2 | Bluetooth: Prevent uninitialized data access in L2CAP configurationnet/ | +15 | 2 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Marcel Holtmann |
|---|---|
| 1/2 | A-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Bug fixes for RFCOMM and L2CAP
Here are two bug fixes forgit://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth.git
The first is a pretty obvious fix where an RFCOMM disconnect timer needs to be cancelled when the disconnect happens earlier. It's not clear why the reference counting logic breaks down if this timer is not cancelled, but it's definitely more correct to cancel the timer.
The L2CAP fix came up due to a buggy PTS test, which was not sending the L2CAP RFC option in an ERTM config response. This was causing access to uninitialized data.
Mat Martineau (2):
Bluetooth: Clear RFCOMM session timer when disconnecting last channel
Bluetooth: Prevent uninitialized data access in L2CAP configuration
net/bluetooth/l2cap_core.c | 16 +++++++++++++++- net/bluetooth/rfcomm/core.c | 1 + 2 files changed, 16 insertions(+), 1 deletions(-)
Signature · 6 lines
1.7.8 -- Mat Martineau Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum