All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Buchberger, Dennis" <dennis.buchberger@hs-osnabrueck.de>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: Problem loading eBPF program on Kernel 4.18 (best with CO:RE): -EINVAL
Date: Wed, 5 Jan 2022 11:43:02 +0100	[thread overview]
Message-ID: <YdV2NgMG/EWwJVQn@kroah.com> (raw)
In-Reply-To: <1641377010132.82356@hs-osnabrueck.de>

On Wed, Jan 05, 2022 at 10:03:30AM +0000, Buchberger, Dennis wrote:
> Hello :)
> 
> I am currently having a problem and hope you can help me: My goal is to develop a BPF-program (see below) on a development machine and then deploy it to another machine to run it there using BPF CO:RE.
> But the program does not load; bpf_object__load returns -EINVAL.
> 
> Development machine:
> - Ubuntu 20.04 LTS
> - Linux 5.4.0-90-generic x86_64
> - Kernel compiled with CONFIG_DEBUG_INFO_BTF=y, so BTF is available under /sys/kernel/btf/vmlinux
> - clang version: 10.0.0-4ubuntu1
> - llc version: 10.0.0
> 
> Target machine:
> - Ubuntu 18.10
> - Linux 4.18.0-25-generic x86_64

4.18 is very old and obsolete and insecure and only supported by the
vendor you are paying support from.  Please upgrade to a more modern
kernel (4.18 was released way back in 2018), if you wish to get help
from the kernel community.

Actually, the vendor you are paying for support to stay at this old
kernel version should be able to provide help to you, why not ask them?

thanks,

greg k-h

  reply	other threads:[~2022-01-05 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 10:03 Problem loading eBPF program on Kernel 4.18 (best with CO:RE): -EINVAL Buchberger, Dennis
2022-01-05 10:43 ` Greg KH [this message]
2022-01-05 18:20   ` AW: [Extern] " Buchberger, Dennis
2022-01-06  4:55 ` Andrii Nakryiko
2022-01-06 16:53   ` AW: [Extern] " Buchberger, Dennis
2022-01-06 20:17     ` Andrii Nakryiko
2022-01-07  9:30       ` AW: " Buchberger, Dennis

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=YdV2NgMG/EWwJVQn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=dennis.buchberger@hs-osnabrueck.de \
    /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.