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

Remove unnecessary recursive locking from Http2Stream.Complete #36030

Merged
merged 1 commit into from
May 8, 2020

Conversation

stephentoub
Copy link
Member

We just asserted we're holding the lock. We don't need to take it again.

cc: @scalablecory

We just asserted we're holding the lock.  We don't need to take it again.
@ghost
Copy link

ghost commented May 7, 2020

Tagging subscribers to this area: @dotnet/ncl
Notify danmosemsft if you want to be subscribed.

Copy link
Member

@wfurt wfurt left a comment

Choose a reason for hiding this comment

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

LGTM.
I guess Debug.Assert() is sufficient to catch code changes, right?

@stephentoub
Copy link
Member Author

I guess Debug.Assert() is sufficient to catch code changes, right?

Yes. And the stuff outside of the lock in this function actually needs to be inside it, so it's necessary that callers lock.

@stephentoub stephentoub merged commit 17cff47 into dotnet:master May 8, 2020
@stephentoub stephentoub deleted the removelock branch May 8, 2020 00:58
@karelz karelz added this to the 5.0.0 milestone Aug 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants