From: Chris Murphy <lists@colorremedies.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: 5:11: in-kernel BTF is malformed
Date: Wed, 3 Feb 2021 17:19:11 -0700 [thread overview]
Message-ID: <CAJCQCtS342b_DAOHswvB6ZwcRa79SoDrNgWDYwOHY4sVPx8pPw@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzZ4oTB0-JizHe1VaCk2V+Jb9jJoTznkgh6CjE5VxNVqbg@mail.gmail.com>
On Wed, Feb 3, 2021 at 4:32 PM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
>
> The important and very relevant part from the bugzilla:
>
> Feb 03 15:06:26 fmac.local kernel: BPF: sched_reset_on_fork
> type_id=6 bitfield_size=0 bits_offset=0
> Feb 03 15:06:26 fmac.local kernel: BPF:
> Feb 03 15:06:26 fmac.local kernel: BPF:Invalid member bits_offset
> Feb 03 15:06:26 fmac.local kernel: BPF:
>
> Do you have full dmesg with output from the BPF verifier?
Full dmesg is attached to the bug. So is the kernel config.
[ 0.000000] Linux version 5.11.0-0.rc6.141.fc34.x86_64
(mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.0.0
20210123 (Red Hat 11.0.0-0), GNU ld version 2.35.1-25.fc34) #1 SMP Mon
Feb 1 13:51:38 UTC 2021
> If you can share the vmlinux itself, that would help as well.
vmlinuz is in this rpm
https://kojipkgs.fedoraproject.org//packages/kernel/5.11.0/0.rc6.141.fc34/x86_64/kernel-core-5.11.0-0.rc6.141.fc34.x86_64.rpm
--
Chris Murphy
next prev parent reply other threads:[~2021-02-04 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 20:26 5:11: in-kernel BTF is malformed Chris Murphy
2021-02-03 22:39 ` Chris Murphy
2021-02-03 23:32 ` Andrii Nakryiko
2021-02-04 0:19 ` Chris Murphy [this message]
2021-02-04 0:46 ` Chris Murphy
2021-02-04 1:00 ` Arnaldo Carvalho de Melo
2021-02-04 1:21 ` Chris Murphy
2021-02-04 2:04 ` Andrii Nakryiko
2021-02-04 2:10 ` Chris Murphy
2021-02-04 13:26 ` Arnaldo Carvalho de Melo
2021-02-04 16:33 ` [FIXED] " Arnaldo Carvalho de Melo
2021-02-05 3:10 ` Chris Murphy
2021-02-05 16:06 ` Arnaldo Carvalho de Melo
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=CAJCQCtS342b_DAOHswvB6ZwcRa79SoDrNgWDYwOHY4sVPx8pPw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.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: 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.