Update go-quark to v0.2.0 #41408
Merged
Update go-quark to v0.2.0 #41408
Conversation
This file contains 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
This version of go-quark includes a bugfix from libquark that fixes kprobes on newer Linux kernels.
mjwolf
added
Auditbeat
bugfix
Team:Security-Linux Platform
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
botelastic
bot
added
needs_team
pierrehilbert
added
the
Team:Elastic-Agent-Data-Plane
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
pierrehilbert
requested review from
mauri870
and removed request for
khushijain21
|
Can we get a quick ok here, we would like this to make it to 8.16 as it fixes a real bug. |
nicholasberlin
approved these changes
Oct 24, 2024
mauri870
approved these changes
Oct 24, 2024
pierrehilbert
approved these changes
Oct 24, 2024
|
@haesbaert we should be able to merge this when the automated tests will be finalized. |
awesome, many thanks! |
mergify bot
pushed a commit
that referenced
this pull request
Oct 24, 2024
Update go-quark to v0.2.0. This version of go-quark includes a bugfix from libquark that fixes use of kprobes on newer Linux kernels. This also removes the license override for go-quark; the license in it should now be detected properly, removing the need for the override. (cherry picked from commit f8d3880)
1 task
mergify bot
pushed a commit
that referenced
this pull request
Oct 24, 2024
Update go-quark to v0.2.0. This version of go-quark includes a bugfix from libquark that fixes use of kprobes on newer Linux kernels. This also removes the license override for go-quark; the license in it should now be detected properly, removing the need for the override. (cherry picked from commit f8d3880)
1 task
pierrehilbert
pushed a commit
that referenced
this pull request
Oct 24, 2024
Update go-quark to v0.2.0. This version of go-quark includes a bugfix from libquark that fixes use of kprobes on newer Linux kernels. This also removes the license override for go-quark; the license in it should now be detected properly, removing the need for the override. (cherry picked from commit f8d3880) Co-authored-by: Michael Wolf <[email protected]>
pierrehilbert
pushed a commit
that referenced
this pull request
Oct 24, 2024
Update go-quark to v0.2.0. This version of go-quark includes a bugfix from libquark that fixes use of kprobes on newer Linux kernels. This also removes the license override for go-quark; the license in it should now be detected properly, removing the need for the override. (cherry picked from commit f8d3880) Co-authored-by: Michael Wolf <[email protected]>
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.
Proposed commit message
Update go-quark to v0.2.0. This version of go-quark includes a bugfix from libquark that fixes use of kprobes
on newer Linux kernels.
This also removes the license override for go-quark; the license in it should now be detected properly, removing the need for the override.
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 files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
None