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

[release/7.0-staging] Fix AwaitableSocketAsyncEventArgs reorderings on weaker memory models #84641

Merged

Conversation

github-actions[bot]
Copy link
Contributor

Backport of #84432 to release/7.0-staging

/cc @stephentoub

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

There are a couple of places where we read the _continuation field and then read some other state which we assume to be consistent with the value we read in _continuation.  But without a fence, those secondary reads could be reordered with respect to the first.
@ghost
Copy link

ghost commented Apr 11, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #84432 to release/7.0-staging

/cc @stephentoub

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-System.Net.Sockets

Milestone: -

@jeffhandley jeffhandley changed the title [release/7.0-staging] [release/6.0] Fix AwaitableSocketAsyncEventArgs reorderings on weaker memory models [release/7.0-staging] Fix AwaitableSocketAsyncEventArgs reorderings on weaker memory models Apr 11, 2023
@jeffhandley jeffhandley added the Servicing-consider Issue for next servicing release review label Apr 11, 2023
@leecow leecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Apr 11, 2023
@leecow leecow added this to the 7.0.7 milestone Apr 11, 2023
@stephentoub
Copy link
Member

@carlossanlop, with this targeting staging, I can merge this now, right?

@carlossanlop
Copy link
Member

Correct.

  • The check-service-labels required CI action is unblocked thanks to the Servicing-approved label.
  • The staging branch is being targeted.
  • The CI failures are linked as known.
  • And you got a couple sign-offs.

Do the honors. Smash the squash&merge button.

@stephentoub stephentoub merged commit 70c91e2 into release/7.0-staging Apr 14, 2023
@stephentoub stephentoub deleted the backport/pr-84432-to-release/7.0-staging branch April 14, 2023 23:32
@ghost ghost locked as resolved and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants