Skip to content

move update_current_secure_channel_state before reporting attest the key#260

Merged
ZhidongPeng merged 1 commit intoAzure:devfrom
ZhidongPeng:dev
Jul 25, 2025
Merged

move update_current_secure_channel_state before reporting attest the key#260
ZhidongPeng merged 1 commit intoAzure:devfrom
ZhidongPeng:dev

Conversation

@ZhidongPeng
Copy link
Collaborator

@ZhidongPeng ZhidongPeng commented Jul 24, 2025

It is a race condition bug, when key_latched and all provisioned, GPA starts the status reporting async task (some other telemetry async tasks too), and then update the secure channel state into shared state. There is a risk, status reporting task could get the current_secure_channel_state from shared state earlier than GPA updated it.
Hence there will be 1 minutes delay our status reporting task to get the updated current_secure_channel_state.

@ZhidongPeng ZhidongPeng enabled auto-merge (squash) July 24, 2025 21:18
@ZhidongPeng ZhidongPeng merged commit 07301b2 into Azure:dev Jul 25, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants