Skip to content

x/sys: v0.14.0 removes definition of BPF_F_KPROBE_MULTI_RETURN in unix/zerrors_linux.go #63969

Closed

Description

@brycekahle

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 Output
$ go env
GO111MODULE="auto"
GOARCH="arm64"
GOBIN=""
GOCACHE="/home/vagrant/.cache/go-build"
GOENV="/home/vagrant/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/vagrant/go/pkg/mod"
GONOPROXY="github.com/DataDog"
GONOSUMDB="github.com/DataDog"
GOOS="linux"
GOPATH="/home/vagrant/go"
GOPRIVATE="github.com/DataDog"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/vagrant/.gimme/versions/go1.20.10.linux.arm64"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/vagrant/.gimme/versions/go1.20.10.linux.arm64/pkg/tool/linux_arm64"
GOVCS=""
GOVERSION="go1.20.10"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
GOWORK=""
CGO_CFLAGS="-I/git/datadog-agent/dev/include"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-L/git/datadog-agent/dev/lib"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1187157903=/tmp/go-build -gno-record-gcc-switches"

What did you do?

Updated golang.org/x/sys dependency to v0.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 an enum in torvalds/linux@c5487f8

Activity

  1. added this to the Unreleased milestone on Nov 6, 2023
  2. added
    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.
    on Nov 6, 2023
  3. bcmills commented on Nov 6, 2023

    @bcmills
    Contributor

    (attn @tklauser)

  4. self-assigned this
    on Nov 6, 2023
  5. added
    NeedsFixThe path to resolution is known, but the work has not been done.
    and removed
    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.
    on Nov 6, 2023
  6. gopherbot commented on Nov 7, 2023

    @gopherbot
    Contributor

    Change https://go.dev/cl/540395 mentions this issue: unix: update BPF constants for Linux kernel 6.6

  7. added a commit that references this issue on Nov 21, 2023
  8. locked and limited conversation to collaborators on Nov 7, 2024
  9. added a commit that references this issue on Feb 13, 2025
    9888904
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions