Skip to content
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

Do not call SignalSession on invalid session IDs #92431

Merged
merged 2 commits into from
Sep 22, 2023

Conversation

davmason
Copy link
Member

Fixes #92098
Fixes #92236

@davmason davmason added this to the 9.0.0 milestone Sep 21, 2023
@davmason davmason requested review from lateralusX and a team September 21, 2023 19:42
@davmason davmason self-assigned this Sep 21, 2023
@ghost
Copy link

ghost commented Sep 21, 2023

Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #92098
Fixes #92236

Author: davmason
Assignees: davmason
Labels:

area-System.Diagnostics.Tracing

Milestone: 9.0.0

@davmason
Copy link
Member Author

/backport to release/8.0-rc2

@github-actions
Copy link
Contributor

Started backporting to release/8.0-rc2: https://github.com/dotnet/runtime/actions/runs/6268145663

Copy link
Member

@lateralusX lateralusX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should close the potential race between EventPipeInternal.SignalSession(m_sessionID) and EventPipeInternal.Disable(sessionID) by grabbing m_dispatchControllLock around call to EventPipeInternal.Disable(sessionID).

@davmason davmason merged commit d59a99e into dotnet:main Sep 22, 2023
171 checks passed
@ghost ghost locked as resolved and limited conversation to collaborators Oct 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.