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

getContainerNetworkInfo: lock netNsCtr before sync #10754

Merged
merged 1 commit into from
Jun 23, 2021

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Jun 22, 2021

syncContainer() requires the container to be locked, otherwise we can
end up with undefined behavior.

[NO TESTS NEEDED]

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 22, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 22, 2021
Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

Other than the nit, LGTM

Thanks!

libpod/networking_linux.go Show resolved Hide resolved
`syncContainer()` requires the container to be locked, otherwise we can
end up with undefined behavior.

[NO TESTS NEEDED]

Signed-off-by: Paul Holzinger <[email protected]>
@Luap99
Copy link
Member Author

Luap99 commented Jun 22, 2021

It does not fix #10090 according to @thmo on IRC

@mheon
Copy link
Member

mheon commented Jun 22, 2021

LGTM, even if this isn't a fix for the issue - this could cause no end of trouble elsewhere at some point.

@mheon
Copy link
Member

mheon commented Jun 22, 2021

/lgtm
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 22, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 22, 2021
@TomSweeneyRedHat
Copy link
Member

Changes LGTM, but one of the TTY tests is failing. I can't imagine it's due to this change, but it doesn't look flakey either....

@vrothberg
Copy link
Member

Changes LGTM, but one of the TTY tests is failing. I can't imagine it's due to this change, but it doesn't look flakey either....

It's a very frequent flake in CI at the moment ( see #10710).

@Luap99
Copy link
Member Author

Luap99 commented Jun 23, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 23, 2021
@openshift-merge-robot openshift-merge-robot merged commit e159eb8 into containers:master Jun 23, 2021
@Luap99 Luap99 deleted the sync-lock branch June 23, 2021 08:35
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants