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

[7.15](backport #28117) Allow clone3 syscall in seccomp filters #28331

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 11, 2021

This is an automatic backport of pull request #28117 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

clone3 is a linux syscall that is now used by glibc starting version
2.34. It is used when pthread_create() gets called. Current seccomp
filters do not allow this syscall leading to crashes like
runtime/cgo: pthread_create failed: Operation not permitted

See elastic/apm-server#6238 for more details

(cherry picked from commit 82507fd)
@mergify mergify bot added the backport label Oct 11, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 11, 2021
@botelastic
Copy link

botelastic bot commented Oct 11, 2021

This pull request doesn't have a Team:<team> label.

@simitt
Copy link
Contributor

simitt commented Oct 12, 2021

/test

@mergify
Copy link
Contributor Author

mergify bot commented Oct 15, 2021

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.15/pr-28117 upstream/mergify/bp/7.15/pr-28117
git merge upstream/7.15
git push upstream mergify/bp/7.15/pr-28117

@jsoriano
Copy link
Member

/test

@simitt
Copy link
Contributor

simitt commented Nov 11, 2021

Looks like this missed the 7.15.2 train.

@botelastic
Copy link

botelastic bot commented Dec 11, 2021

Hi!
We just realized that we haven't looked into this PR in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Dec 11, 2021
@andrewkroh andrewkroh closed this Dec 12, 2021
@mergify mergify bot deleted the mergify/bp/7.15/pr-28117 branch December 12, 2021 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label Stalled
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants