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

[Backport 17.06] Possible race on ingress programming #2195

Merged
merged 1 commit into from
Jun 21, 2018

Conversation

fcrisciani
Copy link

@fcrisciani fcrisciani commented Jun 20, 2018

backport of #2178

Make sure that iptables operations on ingress
are serialized.
Before 2 racing routines trying to create the ingress chain
were allowed and one was failing reporting the chain as
already existing.
The lock guarantees that this condition does not happen anymore

Signed-off-by: Flavio Crisciani flavio.crisciani@docker.com
(cherry picked from commit 7bb62d0)

Make sure that iptables operations on ingress
are serialized.
Before 2 racing routines trying to create the ingress chain
were allowed and one was failing reporting the chain as
already existing.
The lock guarantees that this condition does not happen anymore

Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
(cherry picked from commit 7bb62d0)
@fcrisciani fcrisciani requested a review from ctelfer June 20, 2018 22:00
@andrewhsu
Copy link
Member

@fcrisciani is cherry-pick clean?

@fcrisciani
Copy link
Author

@andrewhsu yep

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

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

LGTM

ping @ctelfer @abhi PTAL

Copy link
Contributor

@ctelfer ctelfer left a comment

Choose a reason for hiding this comment

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

LGTM

@ctelfer ctelfer merged commit f778f4f into moby:bump_17.06 Jun 21, 2018
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.

4 participants