io: allow clear_readiness
after io driver shutdown
#6067
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.
Trying to perform an IO operation after runtime shutdown currently results in an error, and this is intentional. However, if you perform an IO operation, then shut down the runtime, and then call
clear_readiness
, then this does not trigger that error. Instead, it hits an internaldebug_assert!
codepath.We fix this by allowing
clear_readiness
after runtime shutdown.Fixes: #6066