public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106773] libbpf: failed to find BTF info for global/extern symbol 'bpf_link_fops' Date: Thu, 01 Dec 2022 02:07:32 +0000 [thread overview] Message-ID: <bug-106773-4-x6hhXwEKEJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773 --- Comment #7 from James Hilliard <james.hilliard1 at gmail dot com> --- There's also this error during skeleton generation for kfunc_call_test.c: $ /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool --debug gen skeleton /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/kfunc_call_test.bpf.linked3.o name kfunc_call_test libbpf: loading object 'kfunc_call_test' from buffer libbpf: elf: section(2) .symtab, size 648, link 1, flags 0, type=2 libbpf: elf: section(3) .data, size 0, link 0, flags 3, type=1 libbpf: elf: skipping section(3) .data (size 0) libbpf: elf: section(4) .bss, size 0, link 0, flags 3, type=8 libbpf: elf: section(5) tc, size 1120, link 0, flags 6, type=1 libbpf: sec 'tc': found program 'kfunc_call_test2' at insn offset 0 (0 bytes), code size 13 insns (104 bytes) libbpf: sec 'tc': found program 'kfunc_call_test1' at insn offset 13 (104 bytes), code size 21 insns (168 bytes) libbpf: sec 'tc': found program 'kfunc_call_test_ref_btf_id' at insn offset 34 (272 bytes), code size 22 insns (176 bytes) libbpf: sec 'tc': found program 'kfunc_call_test_pass' at insn offset 56 (448 bytes), code size 52 insns (416 bytes) libbpf: sec 'tc': found program 'kfunc_call_test_get_mem' at insn offset 108 (864 bytes), code size 32 insns (256 bytes) libbpf: elf: section(6) syscall, size 152, link 0, flags 6, type=1 libbpf: sec 'syscall': found program 'kfunc_syscall_test' at insn offset 0 (0 bytes), code size 15 insns (120 bytes) libbpf: sec 'syscall': found program 'kfunc_syscall_test_null' at insn offset 15 (120 bytes), code size 4 insns (32 bytes) libbpf: elf: section(7) license, size 4, link 0, flags 3, type=1 libbpf: license of kfunc_call_test is GPL libbpf: elf: section(8) .comment, size 43, link 0, flags 30, type=1 libbpf: elf: skipping unrecognized data section(8) .comment libbpf: elf: section(9) .reltc, size 272, link 2, flags 40, type=9 libbpf: elf: section(10) .relsyscall, size 64, link 2, flags 40, type=9 libbpf: elf: section(11) .BTF, size 467261, link 0, flags 0, type=1 libbpf: looking for externs among 27 symbols... libbpf: failed to find BTF for extern 'bpf_kfunc_call_test2': -22 Error: failed to open BPF object file: Invalid argument
next prev parent reply other threads:[~2022-12-01 2:07 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-29 22:07 [Bug c/106773] New: " james.hilliard1 at gmail dot com 2022-09-01 20:31 ` [Bug target/106773] " james.hilliard1 at gmail dot com 2022-09-01 22:33 ` james.hilliard1 at gmail dot com 2022-11-29 0:44 ` david.faust at oracle dot com 2022-11-30 21:20 ` david.faust at oracle dot com 2022-12-01 0:04 ` james.hilliard1 at gmail dot com 2022-12-01 0:12 ` james.hilliard1 at gmail dot com 2022-12-01 2:07 ` james.hilliard1 at gmail dot com [this message] 2022-12-01 17:09 ` david.faust at oracle dot com 2022-12-01 21:49 ` david.faust at oracle dot com 2022-12-01 22:09 ` james.hilliard1 at gmail dot com 2022-12-01 22:11 ` james.hilliard1 at gmail dot com 2022-12-01 22:30 ` james.hilliard1 at gmail dot com 2022-12-05 17:42 ` david.faust at oracle dot com 2022-12-05 19:01 ` james.hilliard1 at gmail dot com 2022-12-05 21:06 ` david.faust at oracle dot com 2022-12-05 21:57 ` james.hilliard1 at gmail dot com 2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org 2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org 2022-12-14 18:26 ` cvs-commit at gcc dot gnu.org 2023-01-06 14:18 ` jemarch at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-106773-4-x6hhXwEKEJ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).