-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick b341c44: Fix ETW trace logging crash in multithreading situations (#21566) #22430
Open
aamajumder
wants to merge
3
commits into
rel-os-1.19.2
Choose a base branch
from
user/aamajumder/update-rel-os-1.19.2
base: rel-os-1.19.2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
### Description ETW trace logger is fakely registered as initialized_ is marked as true before the registration is done, causing crashing issue for Lenovo camera application. A prior attempt to address was made here: #21226 It was reverted here: #21360 ### Motivation and Context The problem is that during initialization of TraceLoggingRegisterEx, it will reinvoke the callback and attempt reinitialization, which is not allowed. TraceLoggingRegisterEx however can be initialized concurrently when initialization happens on multiple threads. For these reasons it needs to be protected by a lock, but the lock cannot naively block because the callback's reinvocation will cause a deadlock. To solve this problem another tracking variable is added : "initializing" which protects against reinitialization during the first initialization. --------- Co-authored-by: Sheil Kumar <[email protected]>
martinb35
previously approved these changes
Oct 16, 2024
…#21902) ### Description Catch in etw_sink.cc is causing build failures for flavors with EHsc disabled. Remove the catch and set the Failure state as a response the FAILED check. ### Motivation and Context Catch in etw_sink.cc is causing build failures for flavors with EHsc disabled. --------- Co-authored-by: Sheil Kumar <[email protected]>
smk2007
previously approved these changes
Oct 18, 2024
fdwr
previously approved these changes
Oct 19, 2024
fdwr
approved these changes
Oct 22, 2024
@smk2007 Needs a 2nd approving review into release branches. |
smk2007
approved these changes
Oct 23, 2024
Restarted CI, but some of these failures have nothing to do with DML?? "MacOS CI Pipeline" Any thoughts @smk2007? |
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.
Description
ETW trace logger is fakely registered as initialized_ is marked as true before the registration is done, causing crashing issue for Lenovo camera application.
A prior attempt to address was made here:
#21226 It was reverted here:
#21360
Motivation and Context
The problem is that during initialization of TraceLoggingRegisterEx, it will reinvoke the callback and attempt reinitialization, which is not allowed. TraceLoggingRegisterEx however can be initialized concurrently when initialization happens on multiple threads. For these reasons it needs to be protected by a lock, but the lock cannot naively block because the callback's reinvocation will cause a deadlock.
To solve this problem another tracking variable is added : "initializing" which protects against reinitialization during the first initialization.
Description
Motivation and Context