From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Elerion <elerion1000@gmail.com>,
"iovisor-dev@lists.iovisor.org" <iovisor-dev@lists.iovisor.org>
Cc: brouer@redhat.com, "Toke Høiland-Jørgensen" <toke@redhat.com>,
xdp-newbies@vger.kernel.org,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"Yonghong Song" <ys114321@gmail.com>
Subject: Re: Error loading xdp program that worked with bpf_load
Date: Thu, 11 Jun 2020 12:59:52 +0200 [thread overview]
Message-ID: <20200611125952.3527dfdb@carbon> (raw)
In-Reply-To: <CAMDScmnTYKfjMjiqLGduY4Pk3X0D7RQhjtY7DuPmh65VMNeCRw@mail.gmail.com>
(Cross-posting to iovisor-dev)
Seeking input from BPF-llvm developers. How come Clang/LLVM 10+ is
generating incompatible BTF-info in ELF file, and downgrading to LLVM-9
fixes the issue ?
On Wed, 10 Jun 2020 14:50:27 -0700 Elerion <elerion1000@gmail.com> wrote:
> Never mind, I fixed it by downgrading to Clang 9.
>
> It appears to be an issue with Clang/LLVM 10+
>
> https://github.com/cilium/ebpf/issues/43
>
> On Wed, Jun 10, 2020 at 2:38 PM Toke Høiland-Jørgensen <toke@redhat.com> wrote:
> >
> > Elerion <elerion1000@gmail.com> writes:
> >
> > > [69] FUNC xdp_program type_id=68 vlen != 0
> >
> > 'vlen != 0' is the error. Not sure why you hit that; what's the output
> > of 'bpftool btf dump file yourprog.o' ?
> >
> > -Toke
> >
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2020-06-11 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 21:01 Error loading xdp program that worked with bpf_load Elerion
2020-06-10 21:06 ` Toke Høiland-Jørgensen
2020-06-10 21:08 ` Elerion
2020-06-10 21:37 ` Toke Høiland-Jørgensen
2020-06-10 21:44 ` Elerion
2020-06-10 21:50 ` Elerion
2020-06-11 10:59 ` Jesper Dangaard Brouer [this message]
2020-06-11 16:34 ` Andrii Nakryiko
2020-06-11 16:39 ` [iovisor-dev] " Alexei Starovoitov
2020-06-11 20:40 ` Elerion
2020-06-11 20:46 ` Andrii Nakryiko
2020-06-11 21:11 ` Elerion
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=20200611125952.3527dfdb@carbon \
--to=brouer@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=elerion1000@gmail.com \
--cc=iovisor-dev@lists.iovisor.org \
--cc=toke@redhat.com \
--cc=xdp-newbies@vger.kernel.org \
--cc=ys114321@gmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.