-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Don't close session or update key id on spurious resolve #10917
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the device already has or is setting up a case session, there's no reason to close it and persist a new key id just because we got an mdns input. If an mdns resolution comes in during a case session establishment, this will cause an error.
PR #10917: Size comparison from 3c8b7e6 to 7b645dc 20 builds (for efr32, k32w, linux, p6, qpg, telink)
10 builds (for nrfconnect)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
If we receive a second address update completion while we're establishing a case session already, the call to device->OperationalCertProvisioned() closes the session while it is being established and causes an error.
Fixes #10772 (though I make no assurances that there are no other race conditions in the code).
Change overview
Adds a check around device->OperationalCertProvisioned() such that we don't call this function if we have a secure connection already set up or in the process of being set up.
Testing
Because of #10771, I had a local cirque instance where the case establishment from the subscription thread was reliably conflicting with the UpdateNode call later in the test. This race doesn't appear to happen in the presubmits (gotta love race bugs). Adding this check fixed the race condition on my local cirque tests.