-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ble: Fix persistence in SecurityDB #13942
Conversation
@paul-szczepanek-arm, thank you for your changes. |
flags->connected = true; | ||
|
||
/* update peer address */ | ||
SecurityDistributionFlags_t* old_flags = get_distribution_flags(*db_handle); |
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.
Does it matter to update the peer address ?
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.
yes, address changed, otherwise we would've found it by address
CI started |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
There is a set of bugs that interfere with BLE bonding persistence.
The connected flag was is not being updated when entry are found. This sets the flag at appropriate places.
It also updates the peer address if the entry found based on EDIV and Rand does not match the peer address.
The KVStore Security db implementation initialises indices in the array of entries incorrectly. This removes the index altogether and uses the memory address to get the index instead.
Impact of changes
Migration actions required
Documentation
none
Pull request type
Test results
Reviewers