libbeat: add 'eventfd2' to default seccomp policy#46372
Merged
AndersonQ merged 7 commits intoelastic:mainfrom Sep 8, 2025
Merged
libbeat: add 'eventfd2' to default seccomp policy#46372AndersonQ merged 7 commits intoelastic:mainfrom
AndersonQ merged 7 commits intoelastic:mainfrom
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
911674b to
d0078f2
Compare
44abf81 to
1892a43
Compare
1892a43 to
45371ed
Compare
AndersonQ
commented
Sep 4, 2025
45371ed to
5f31562
Compare
Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path.
5f31562 to
de0ad4a
Compare
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
mauri870
approved these changes
Sep 5, 2025
Contributor
|
This pull request is now in conflicts. Could you fix it? 🙏 |
mergify bot
pushed a commit
that referenced
this pull request
Sep 8, 2025
* libbeat: add 'eventfd2' to default seccomp policy Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go
mergify bot
pushed a commit
that referenced
this pull request
Sep 8, 2025
* libbeat: add 'eventfd2' to default seccomp policy Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go
mergify bot
pushed a commit
that referenced
this pull request
Sep 8, 2025
* libbeat: add 'eventfd2' to default seccomp policy Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go
mergify bot
pushed a commit
that referenced
this pull request
Sep 8, 2025
* libbeat: add 'eventfd2' to default seccomp policy Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go
3 tasks
AndersonQ
added a commit
that referenced
this pull request
Sep 9, 2025
* libbeat: add 'eventfd2' to default seccomp policy Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go
AndersonQ
added a commit
that referenced
this pull request
Sep 9, 2025
…icy (#46450) * libbeat: add 'eventfd2' to default seccomp policy (#46372) Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go * fix merge conflicts --------- Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
AndersonQ
added a commit
that referenced
this pull request
Sep 9, 2025
…licy (#46448) * libbeat: add 'eventfd2' to default seccomp policy (#46372) Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go * fix merge conflicts --------- Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
AndersonQ
added a commit
that referenced
this pull request
Sep 9, 2025
…licy (#46447) * libbeat: add 'eventfd2' to default seccomp policy (#46372) Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go --------- Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
AndersonQ
added a commit
that referenced
this pull request
Sep 10, 2025
…icy (#46449) * libbeat: add 'eventfd2' to default seccomp policy (#46372) Since Go introduced https://go.dev/cl/560615 it uses `eventfd2`, which was not part of our default seccomp policy. Due to the `google.golang.org/protobuf` dependency `eventfd2` during its initialisation, before our seccomp policy be applied, thus it worked. However once filebeat is reexeced, for example, due to a CA change, the seccomp policy would be in place and prevent `eventfd2` call, crashing filebeat. This change adds `eventfd2` to the default seccomp policy This also adjusts Beat.doReexec to use os.Executable isntead of manually building the binary path. (cherry picked from commit 7162773) # Conflicts: # libbeat/tests/integration/elasticsearch_test.go * fix merge conflicts * add line break * fix linting issue --------- Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'll add the known issue in another PR as it affects other versions
Proposed commit message
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
How to test this PR locally
follow the steps outlined in the bug on how to reproduce the issue:
restart_on_cert_changeconsistently causes crash #46333Related issues
restart_on_cert_changeconsistently causes crash #46333Use cases