-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 :Mesh:Provison init should after proxy #22207
Labels
area: Bluetooth Mesh
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Comments
You're right, this looks like a real bug - I'm surprised no one has noticed since it results in the provisioning buffer having |
@moringe can you confirm that the following would solve the issue:
|
jhedberg
pushed a commit
to jhedberg/zephyr
that referenced
this issue
Jan 27, 2020
When PB-GATT support has been enabled the provisioning code "borrows" the buffer from the proxy code. However, the way that initialization was happening the proxy buffers were initialized only after provisioning initialization, resulting in a corrupted buffer with buf->data pointing to NULL. Reorder the initialization calls so that proxy is done first and provisioning only after it. Fixes zephyrproject-rtos#22207 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
jhedberg
pushed a commit
that referenced
this issue
Jan 29, 2020
When PB-GATT support has been enabled the provisioning code "borrows" the buffer from the proxy code. However, the way that initialization was happening the proxy buffers were initialized only after provisioning initialization, resulting in a corrupted buffer with buf->data pointing to NULL. Reorder the initialization calls so that proxy is done first and provisioning only after it. Fixes #22207 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Bluetooth Mesh
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
zephyr/subsys/bluetooth/mesh/main.c
Lines 292 to 328 in bce3354
Provision use pb-gatt use buffer from proxy client, however proxy client init after prov init. Prov init call reset_state to allocate buf from proxy client, get-proxy-buf call net_buf_simple_reset to init buf->data = buf->__buf, but at this time buf->__buf currently not initiating.
The text was updated successfully, but these errors were encountered: