Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 18, 2024

@ebpf

Quark was falling back into kprobe since ebpf would fail with EPERM at memfd_create(2).

$ strace -f auditbeat ....
[pid  2917] memfd_create("libbpf-placeholder-fd", MFD_CLOEXEC) = -1 EPERM (Operation not permitted)

With this my test case where kprobe is disabled now uses ebpf when I select backend "auto", before it was falling back to procfsprovider.

Proposed commit message

Checklist

  • My code follows the style guidelines of this project
  • 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 in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

Change QQ_ALL_BACKENDS to QQ_EBPF and kerneltracingprovider will fallback into procfs, with the fix it doesn't.


This is an automatic backport of pull request #41297 done by [Mergify](https://mergify.com).

…@ebpf (#41297)

Quark was falling back into kprobe since ebpf would fail with EPERM at
memfd_create(2).

```
$ strace -f auditbeat ....
[pid  2917] memfd_create("libbpf-placeholder-fd", MFD_CLOEXEC) = -1 EPERM (Operation not permitted)
```

With this my test case where kprobe is disabled now uses ebpf when I select
backend "auto", before it was falling back to procfsprovider.

(cherry picked from commit 6766cfa)
@mergify mergify bot requested a review from a team as a code owner October 18, 2024 14:33
@mergify mergify bot added the backport label Oct 18, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 18, 2024
@botelastic
Copy link

botelastic bot commented Oct 18, 2024

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

@mergify
Copy link
Contributor Author

mergify bot commented Oct 21, 2024

This pull request has not been merged yet. Could you please review and merge it @haesbaert? 🙏

@mergify
Copy link
Contributor Author

mergify bot commented Oct 28, 2024

This pull request has not been merged yet. Could you please review and merge it @haesbaert? 🙏

@haesbaert haesbaert enabled auto-merge (squash) October 28, 2024 08:25
@haesbaert haesbaert merged commit c061d0a into 8.x Oct 28, 2024
@haesbaert haesbaert deleted the mergify/bp/8.x/pr-41297 branch October 28, 2024 08:53
@khushijain21 khushijain21 mentioned this pull request Jun 23, 2025
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants