[L0] fix a deadlock on a recursive event rwlock #1468
Merged
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.
L0, when creating a list of events to wait on, in some cases was first grabbing a lock on a potentially completed event, and then tried to get a command list, which sometimes needs to cleanup all completed events. This caused a deadlock.
This patch moves getting a command list to before the event lock. But because the lock is required to decide whether this command list actually needed, we might be wasting time here.