-
Notifications
You must be signed in to change notification settings - Fork 734
Bluetooth: Post-upmerge bugfixes for v1.5 #457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth: Post-upmerge bugfixes for v1.5 #457
Conversation
As network_decode needs a target buffer for decoding, the max PDU length must be checked to prevent overflow on the target buffer. When receiving a proxy configuration message with excessive length, there's no previous check for this. Also pulls the NET PDU length defines out into net.h, so they can be used when defining the target buffers. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
After #31176, the network would get stored immediately in bt_mesh_net_create, causing the address and devicekey to get stored as their zero-initialized version, as they're only being set in the bt_mesh_comp_provision call, which fires after. Fixes #32067. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
|
Compliance failures are all on commit title length. |
EDIT: nvm :P |
tejlmand
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pulls in 3 Bluetooth Mesh bugfix PRs and one controller bugfix PR from upstream:
* [zephyrproject-rtos/zephyr#32069](https://github.com/zephyrproject-rtos/zephyr/pull/32069) (merged upstream) * [zephyrproject-rtos/zephyr#31909](https://github.com/zephyrproject-rtos/zephyr/pull/31909) (merged upstream) * [zephyrproject-rtos/zephyr#32080](https://github.com/zephyrproject-rtos/zephyr/pull/32080) (pending upstream) * [zephyrproject-rtos/zephyr#32160](https://github.com/zephyrproject-rtos/zephyr/pull/32160) (pending upstream)
Note, all PRs mentioned have been merged upstream, so you may change all the commits in this PR to [nrf fromtree]
you can still line wrap the title as it is done in other commits. Merging a PR with compliance failure causes all later PRs to fail in same way. |
tejlmand
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix title length, so we don't end in the situation where all subsequent PRs starts to fail compliance.
… ... ... initialization Fix missing advertising PDU length initialization which prevented advertising PDU to be transmitted by Radio. This issue was reproduced when connectable undirected advertising was enabled without setting an advertising data. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
... friend msg Set app_idx and net_idx in the msg_ctx before calling bt_mesh_keys_resolve when re-encrypting friend messages, as they'll be referenced inside the function. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
... friend Sets the sequence number when re-encrypting messages from the friend to the lpn. This is a regression from #28511. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
a9b0084 to
709aa11
Compare
tejlmand
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Included in #459
Pulls in 3 Bluetooth Mesh bugfix PRs and one controller bugfix PR from upstream: