Reserve native capacity for linger revocation - #197
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Four blocked user-token requests exhausted native admission and prevented disable-linger from revoking a grant. Explicit revocation now has one independently reserved, tracked native slot; ordinary enable/logon work cannot borrow it. A second revocation remains bounded and overload preserves the RPC busy code.
The public wire regression reproduces the old failure, holds token and account lookup work, checks rejection at both class budgets, validates a coherent snapshot with all eight native slots occupied, and verifies grant/process cleanup while ordinary work stays blocked. The existing store I/O serialization and native-call limitations are unchanged.
Validation: twenty focused race repetitions, full uncached race suite, vet and Windows/Linux staticcheck passed. Three combined revocation/control/native-maintenance repetitions passed after integration. Exact-source CI 34763167061 passed at
86bd7e27cffe7e7cd8b53e5effff137dfdd10502. Six control/ownership cases passed ten times each under SYSTEM and a headless standard user (2.067/0.866 seconds), without skips and with final process/profile cleanup. These exercise delayed adapters under real identities; earlier S4U qualification remains separate.