-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/sys: v0.14.0 removes definition of BPF_F_KPROBE_MULTI_RETURN in unix/zerrors_linux.go #63969
Labels
Milestone
Comments
bcmills
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Nov 6, 2023
(attn @tklauser) |
tklauser
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Nov 6, 2023
Change https://go.dev/cl/540395 mentions this issue: |
1 task
DmitriyMV
added a commit
to DmitriyMV/siderolink
that referenced
this issue
Nov 7, 2023
Wait for golang/go#63969 to resolve. Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
This was referenced Nov 7, 2023
1 task
tklauser
added a commit
to cilium/cilium
that referenced
this issue
Nov 9, 2023
Updating golang.org/x/sys/unix to the recently releases v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to unblock #28994 and allow renovate to update other dependencies. Signed-off-by: Tobias Klauser <tobias@cilium.io>
tklauser
added a commit
to cilium/cilium
that referenced
this issue
Nov 9, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to unblock #28994 and allow renovate to update other dependencies. Signed-off-by: Tobias Klauser <tobias@cilium.io>
tklauser
added a commit
to tklauser/ebpf
that referenced
this issue
Nov 9, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969 and cilium#1206. This was fixed upstream in https://go.dev/cl/540395, so manually pull in the latest unreleased version to allow modules depending on cilium/ebpf to update to later versions as well. Signed-off-by: Tobias Klauser <tobias@cilium.io>
lmb
pushed a commit
to cilium/ebpf
that referenced
this issue
Nov 9, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969 and #1206. This was fixed upstream in https://go.dev/cl/540395, so manually pull in the latest unreleased version to allow modules depending on cilium/ebpf to update to later versions as well. Signed-off-by: Tobias Klauser <tobias@cilium.io>
tklauser
added a commit
to cilium/cilium
that referenced
this issue
Nov 9, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to unblock #28994 and allow renovate to update other dependencies. Signed-off-by: Tobias Klauser <tobias@cilium.io>
This was referenced Nov 9, 2023
This was referenced Nov 15, 2023
1 task
rolinh
added a commit
to cilium/hubble
that referenced
this issue
Nov 15, 2023
Updating `golang.org/x/sys/unix` to the recently released v0.14.0 breaks the build because of the missing definition of `BPF_F_KPROBE_MULTI_RETURN`, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to allow renovate to update other dependencies. Signed-off-by: Robin Hahling <robin.hahling@gw-computing.net>
rolinh
added a commit
to cilium/hubble
that referenced
this issue
Nov 15, 2023
Updating `golang.org/x/sys/unix` to the recently released v0.14.0 breaks the build because of the missing definition of `BPF_F_KPROBE_MULTI_RETURN`, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to allow renovate to update other dependencies. Signed-off-by: Robin Hahling <robin.hahling@gw-computing.net>
sujoshua
pushed a commit
to sujoshua/cilium
that referenced
this issue
Nov 16, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to unblock cilium#28994 and allow renovate to update other dependencies. Signed-off-by: Tobias Klauser <tobias@cilium.io>
nicoche
added a commit
to koyeb/kuma
that referenced
this issue
Nov 21, 2023
pjablonski123
pushed a commit
to pjablonski123/cilium
that referenced
this issue
Dec 15, 2023
Updating golang.org/x/sys/unix to the recently released v0.14.0 will break the build because of the missing definition of BPF_F_KPROBE_MULTI_RETURN, see golang/go#63969. This was fixed upstream, so manually pull in the latest unreleased version to unblock cilium#28994 and allow renovate to update other dependencies. Signed-off-by: Tobias Klauser <tobias@cilium.io>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
What version of Go are you using (
go version
)?go version go1.20.10 linux/arm64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Updated
golang.org/x/sys
dependency tov0.14.0
What did you expect to see?
Continued definition of
BPF_F_KPROBE_MULTI_RETURN
What did you see instead?
Error: /home/runner/go/pkg/mod/github.com/cilium/ebpf@v0.12.2/internal/unix/types_linux.go:41:36: undefined: linux.BPF_F_KPROBE_MULTI_RETURN
This commit removed the definition. This is likely because it was changed from a
#define
to anenum
in torvalds/linux@c5487f8The text was updated successfully, but these errors were encountered: