Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
New
|
Undecided
|
Leo Lin | ||
linux (Ubuntu) |
New
|
Undecided
|
Leo Lin | ||
Jammy |
New
|
Undecided
|
Leo Lin | ||
Noble |
New
|
Undecided
|
Leo Lin |
Bug Description
SRU Jusitification for Kernel
[Impact]
Noble failed the L2CAP/LE/
This is due to new behavior introduced in e4b019515f950b4
However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b
[1] https:/
[2] https:/
[Fix]
Backport the from commit 806a5198c05987b
[1] https:/
[Test Case]
1. Install the kernel with the backported patch
2. Run the following test case in the PTS:
L2CAP/
GAP/CONN/
[Where problems could occur]
This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4
Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes.
[1] https:/
Changed in linux (Ubuntu): | |
assignee: | nobody → Leo Lin (0xff07) |
tags: | added: jammy noble |
description: | updated |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → Leo Lin (0xff07) |
Changed in linux (Ubuntu Noble): | |
assignee: | nobody → Leo Lin (0xff07) |
Changed in oem-priority: | |
assignee: | nobody → Leo Lin (0xff07) |