Fix handling of add uevents during scanning #318
Merged
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
Ensure that the enumeration is completed before processing any uevent. This is to avoid a race where the kernel is still enumerating the devices and send the uevent while the parent is being authorised. To not lose these uevents, we store them in a backlog that is processed at the end of the scanning.
This was referenced Aug 5, 2019
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.
Ensure that the enumeration is completed before processing any uevent. This is to avoid a race where the kernel is still enumerating the devices and send the uevent while the parent is being authorised.
To not lose these uevents, we store them in a backlog that is processed at the end of the scanning.
Fixes the test case described in #315