chore(deps): bump github.com/cilium/ebpf from 0.16.0 to 0.17.1

[dependabot]

Bumps github.com/cilium/ebpf from 0.16.0 to 0.17.1.

Release notes

Sourced from github.com/cilium/ebpf's releases.

Hotfix: don't retry endlessly on verifier errors on kernels <6.4

During the prior removal of ProgramOptions.LogSize in v0.16, the tests weren't updated to exercise the retry logic. With the last-minute addition of ProgramOptions.LogSizeStart, a bug was introduced that would cause program loads to retry indefinitely without ever growing the buffer in case of a verifier error on kernels before 6.4. This is now fixed, and the tests were updated to exercise the retry logic.

• prog: fix shadowing log size variable in verifier log retry loop by @​ti-mo in cilium/ebpf#1635

Global Variables, Decl Tags, and package pin

Note: the hotfix release 0.17.1 is out. Users are highly encouraged to upgrade.

As we close the door on the year 2024, we're also wrapping up the ebpf-go v0.17 development cycle. This release represents a large body of work and is our largest feature release since BTF.

Users are, as always, highly encouraged to upgrade, and we're looking forward to hearing your feedback on the new Global Variables API. We've been putting this interface trough its paces internally, along with a few eager community members, and we're ready to let the wider community make use of it.

This release also marks the end of our Go 1.21 support; Go 1.22 is required going forward.

Breaking Changes

Before we get to the fun stuff, we need to call out a few breaking changes:

• Global variables with a static qualifier can no longer be rewritten using CollectionSpec.RewriteConstants()! See the section on global variables under major features below.

• program: remove LogSize and VerifierError.Truncated by @​lmb in cilium/ebpf#1526

• prog: add ProgramOptions.LogSizeStart to obtain full log after verifier bug by @​ti-mo in cilium/ebpf#1630

  The ProgramOptions.LogSize field was deprecated and a no-op since 0.16 and has now been removed completely. In its place, a new field was added to obtain full verifier logs when the verifier hits an internal bug. The ProgramOptions.LogSizeStart field controls the starting size of the log buffer. Use this if you have a good understanding of the log size you're expecting, or if you're trying to pull out the full log when the verifier hits an internal bug. The error string now also contains some hints about what happened and how to handle this situation.

• map: remove MapSpec.Freeze field by @​ti-mo in cilium/ebpf#1558

• elf_reader: don't use BPF_F_RDONLY_PROG flag to trigger map freezing by @​ti-mo in cilium/ebpf#1568

  The Freeze field was ambiguous from the start, and has been a source of subtle bugs over the years. Automatic map freezing is now done based solely on map name (.(ro)data prefix). If you were manually setting this flag, consider using a conventional map name instead.

• info: expose ksym info and func info by ProgramInfo by @​Asphaltt in cilium/ebpf#1576

• info: expose more prog jited info by @​Asphaltt in cilium/ebpf#1598

  Some ext_info types in package btf were redefined to enable pulling raw func and line infos out of Program.Info(). These were all types without methods and all unexported fields, but calling them out regardless in case someone's doing unintended advanced things with BTF.

• kallsyms: change Modules caching strategy, cache address lookups by @​ti-mo in cilium/ebpf#1590

  Users attaching bpf programs to kernel symbols should see a marked decrease in allocations made in the library during program creation in the general case. Only used entries are now cached, making kallsyms lookups on subsequent program loads free. In the pathological case (new kernel symbols on every load), scanning is repeated, resulting in more CPU time being used instead of holding on to all kallsyms symbols indefinitely. ProgramSpec.KernelModule() was unexported until further notice.

  Also, bpf2go users should now be able to generate Go bindings as unprivileged users once again. Oops!

Major Features

Easy global variables: introducing ebpf.VariableSpec and ebpf.Variable

• CollectionSpec: add new Variables field to interact with constants and global variables by @​ti-mo in cilium/ebpf#1564
• Collection: add Variables field to interact with global variables by @​ti-mo in cilium/ebpf#1572
• bpf2go: generate assignment structs and Go types for Variables and VariableSpecs by @​smagnani96 in cilium/ebpf#1610

This has been a frequent ask in the community for years, so we finally bit the bullet and committed to an API to interact with global bpf variables through CollectionSpec.Variables and CollectionSpec.Variables. We've published a small guide over on ebpf-go.dev/concepts/global-variables that details how to use them, so we're not going to reiterate here.

... (truncated)

Commits

• e439d37 prog: fix shadowing log size variable in verifier log retry loop
• 228bb4e examples: tcx: use Variable API
• 580ff21 bpf2go: generate Go types used in global variables
• 1e8f079 bpf2go: generate assignment structs for Variables and VariableSpecs
• c37b7af bpf2go: test: remove unused typesEqualComparer function
• 97cfce5 map: automatically set CPUMap MaxEntries based on possible CPUs
• e8b05c5 prog: add ProgramOptions.LogSizeStart to obtain full log after verifier bug
• f283106 internal: add Between function for clamping a value between min and max
• 6546014 README.md: add pin package to the overview
• 60405bb examples: annotate ringbuf and perf event arrays with value type information
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Reviewer Checklist

🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
If something doesn't apply please check the box and add a justification if the reason is non obvious.

• Is the PR title satisfactory? Is this part of a larger feature and should be grouped using > Changelog?
• PR description is clear and complete. It Links to relevant issue as well as docs and UI issues
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as an image registry)
• IPv6 is taken into account (.e.g: no string concatenation of host port)
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Don't forget ci/ labels to run additional/fewer tests
• Does this contain a change that needs to be notified to users? In this case, UPGRADE.md should be updated.
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)