chore(deps): update go updates #78
Open
+113
−113
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
|
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
11 times, most recently
from
52f5a3d to
4f2dacb
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
14 times, most recently
from
f7e5258 to
76c8d33
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
4 times, most recently
from
cfe59db to
e14d165
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
21 times, most recently
from
4882e16 to
168da61
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
4 times, most recently
from
2160014 to
caf2920
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
3 times, most recently
from
efe4830 to
c3b7761
Compare
Signed-off-by: redhat-renovate-bot <[email protected]>
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
from
c3b7761 to
528b70d
Compare
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.
This PR contains the following updates:
v2.2.0->v2.3.0v5.3.0->v7.2.0v0.9.1->v0.17.1v1.0.3->v1.0.4v1.7.19->v1.8.0v0.1.0->v1.0.0v1.2.5->v1.2.7v0.2.4->v0.3.6v3.11.0->v3.12.1v2.0.0+incompatible->v3.0.0v5.6.0->v5.9.0v0.10.0->v0.13.0v0.5.1->v0.6.0v1.4.1->v1.4.2v1.2.6->v1.3.0v0.19.6->v0.21.0v0.20.2->v0.21.0v0.22.3->v0.23.0v5.0.6->v5.1.0v1.2.0->v1.2.3v0.50.0->v0.51.0v0.6.8->v0.6.94bb14d4->40e02aav0.3.15->v1.0.1v0.0.9->v0.0.24v0.7.7->v0.9.0v1.0.4->v2.0.063d38b5->9ace650f784269->9b43ea0v0.2.0->v0.5.0v0.7.1->v0.7.2v2.11.0->v2.22.2v1.27.10->v1.36.2v1.1.13->v1.2.3v1.10.0->v1.11.1ce21e3f->d6d8306v0.0.0->v3.9.0+incompatible3f1513d->35abaf5v0.0.0-20190128024246-5eb7ae5bdb7a->v0.29.0v0.68.0->v0.79.2v1.16.0->v1.20.5v0.4.0->v0.6.1v0.44.0->v0.61.0v0.11.0->v0.15.1v1.9.0->v1.10.0v1.1.0->v1.3.0v0.0.4->v0.0.5v0.17.0->v0.22.0v0.26.0->v0.33.0v0.18.0->v0.24.0v0.21.0->v0.28.0v0.21.0->v0.27.0v0.16.0->v0.21.0v0.3.0->v0.8.0v0.21.1-0.20240508182429-e35e4ccd0d2d->v0.28.0v1.6.8->v2.0.6fc5f0ca->6982302v1.64.1->v1.69.2v1.34.1->v1.36.1v2.4.0->v3.0.1v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.3->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v8.0.0+incompatible->v11.0.0+incompatiblev0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0c0856e2->2b36238v0.4.0->v2.130.1v2.100.1->v2.130.1v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.02695361->2c72e55v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v1.28.12->v1.32.0v0.28.12->v0.30.8v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.0v0.28.12->v0.32.03b25d92->24370bev1.2.0->v1.4.0v1.2.3->v1.3.0v1.57.0-alpha1->v1.61.0v0.2.6->v0.2.7v0.0.0-20220329064328-f3cc58c6ed90->v0.2.4v0.0.0-20220329064328-f3cc58c6ed90->v0.2.4v0.16.3->v0.19.3bc3834c->cfa47c3v4.3.0->v4.5.0v1.3.0->v1.4.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cespare/xxhash (github.com/cespare/xxhash/v2)
v2.3.0Compare Source
checkpoint-restore/go-criu (github.com/checkpoint-restore/go-criu/v5)
v7.2.0Compare Source
What's Changed
New Contributors
Full Changelog: checkpoint-restore/go-criu@v7.1.0...v7.2.0
v7.1.0Compare Source
What's Changed
protogetterby @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/153crit exploreby @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/158Full Changelog: checkpoint-restore/go-criu@v7.0.0...v7.1.0
v7.0.0Compare Source
What's Changed
stylecheckto golangci-lint by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/128pagesIDfield inMemoryReaderstruct by @behouba in https://github.com/checkpoint-restore/go-criu/pull/142FindPsmethod onPsTreeby @behouba in https://github.com/checkpoint-restore/go-criu/pull/145crit x skfor sockets by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/138New Contributors
Full Changelog: checkpoint-restore/go-criu@v6.3.0...v7.0.0
v6.3.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.2.0...v6.3.0
v6.2.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.1.0...v6.2.0
v6.1.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.0.0...v6.1.0
v6.0.0Compare Source
What's Changed
unmarshalPagemap(), use stdout for CLI output by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/78Full Changelog: checkpoint-restore/go-criu@v5.3.0...v6.0.0
cilium/ebpf (github.com/cilium/ebpf)
v0.17.1: Hotfix: don't retry endlessly on verifier errors on kernels <6.4Compare Source
During the prior removal of
ProgramOptions.LogSizein v0.16, the tests weren't updated to exercise the retry logic. With the last-minute addition ofProgramOptions.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.v0.17.0: Global Variables, Decl Tags, and packagepinCompare Source
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
staticqualifier can no longer be rewritten usingCollectionSpec.RewriteConstants()! See the section on global variables under major features below.program: remove LogSize and VerifierError.Truncated by @lmb in https://github.com/cilium/ebpf/pull/1526
prog: add ProgramOptions.LogSizeStart to obtain full log after verifier bug by @ti-mo in https://github.com/cilium/ebpf/pull/1630
The
ProgramOptions.LogSizefield 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. TheProgramOptions.LogSizeStartfield 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 https://github.com/cilium/ebpf/pull/1558
elf_reader: don't use BPF_F_RDONLY_PROG flag to trigger map freezing by @ti-mo in https://github.com/cilium/ebpf/pull/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 https://github.com/cilium/ebpf/pull/1576
info: expose more prog jited info by @Asphaltt in https://github.com/cilium/ebpf/pull/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 doingunintendedadvanced things with BTF.kallsyms: change Modules caching strategy, cache address lookups by @ti-mo in https://github.com/cilium/ebpf/pull/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.VariableSpecandebpf.VariableThis 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.VariablesandCollectionSpec.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.See the documentation on the use of the
staticqualifier! These are no longer considered global variables, and can't be modified at runtime.bpf2go now also generates objects to be used with
CollectionSpec.Assignand.LoadAndAssign(), and also emits Go type declarations for C types used as bpf C variables. Our test coverage was somewhat lacking for the latter, please drop something on the issue tracker if you're noticing surprising bpf2go output.Note that it's currently not possible to manually create a
VariableSpecand wire it up to aCollectionSpec, so if you were previously relying on e.g. manually assembling aCollectionSpecand usingRewriteConstants()in tests, this will no longer work. This may land as the API crystallizes and we settle on a good mechanism to enable this. Please reach out on the Cilium Slack if you'd like to see this happen.Tags!
As you'll notice, the
btf.Struct,btf.Union,btf.Member,btf.Typedef,btf.Funcandbtf.Varhave gained a new field:Tags! Set one or more tags on these objects from bpf C using__attribute__((btf_decl_tag("mytag")))andyou'll find
Tagsbeing populated in Go.There's also the
btf.Func.ParamTagsfield that holds tags declared on individual function parameters. These are part of theFuncsince they appear only in the function prototype, not in the parameter type itself, since those can appear in many different types. (it does get confusing!)Also, an honorable mention to
btf.TypeTag, which has now been exported. This allows tagging pointers with an arbitrary string value and is mainly used by the Linux verifier to tag kernel pointers, see the__kptrand__kptr_refmacros in Linux'bpf_helpers.h.Pins!
We've added a new root-level package
pin, which currently features theLoad()andWalkDir()functions. Since allLoadPinned*functions in the library now check for the underlying object's type, we've repurposed the machinery to allow loading an opaque pin and returning a Go object of the right type.WalkDirdoes what it says on the tin, it walks bpffs directories and invokes a callback that received the loaded object. Super convenient!Minor Features
We've also added a handful of minor features during this release:
bpf_prog_infofields inProgramInfoby @tyrone-wu in https://github.com/cilium/ebpf/pull/1512Other Changes
Last but not least, there's bugfixes, CI changes and some internal refactoring that happened to eventually make ebpf-go work with ebpf-for-windows. See individual PRs for more context. Stay tuned!
objNameAllowsDot, return *btf.Var fromVariable{Spec}.Type()by @ti-mo in https://github.com/cilium/ebpf/pull/1612epoll.Waitby using sentinel errors by @def in https://github.com/cilium/ebpf/pull/1619New Contributors
Full Changelog: cilium/ebpf@v0.16.0...v0.17.0
v0.16.0Compare Source
program: automatic verifier log sizing and ProgramInfo.RecursionMisses()
For the longest time users had to specify
ProgramOptions.LogSizeto get thefull verifier log for large programs. The library now automatically figures out
the correct buffer size to use and the field is deprecated. It will be removed
in the next version.
ProgramInfo now exposes how often a program didn't execute due to recursion
limits via
RecursionMisses.perf, ringbuf: better control over wakeups, Flush()
There is a trade off between how fast samples are processed and how much CPU is
used. Reading samples as quickly as possible uses more CPU, reading in batches
is cheaper.
It's now possible to configure a "maximum time before a wakeup" by using
Reader.SetDeadline(). This now guarantees that any pending samples are read
at the end of the deadline, even if the Watermark wasn't reached.
It's also possible to manually flush the buffer using
Flush().Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.