From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: bpf@vger.kernel.org
Subject: Re: 5:11: in-kernel BTF is malformed
Date: Wed, 3 Feb 2021 15:39:00 -0700 [thread overview]
Message-ID: <CAJCQCtRHOidM7Vps1JQSpZA14u+B5fR860FwZB=eb1wYjTpqDw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtSQLc0VHqO4BY_-YB2OmCNNmHCS6fNdQKmMWGn2v=Jpdw@mail.gmail.com>
On Wed, Feb 3, 2021 at 1:26 PM Chris Murphy <lists@colorremedies.com> wrote:
>
> qemu-kvm VM starts with kernel 5.10.10 but fails with 5.11.0-rc5.
>
> Libvirt folks think this is a kernel bug, and have attached a
> reproducer to the downstream bug report.
>
> "I've managed to reproduce and found that virBPFLoadProg() logs the
> following message:
>
> in-kernel BTF is malformed\nprocessed 0 insns (limit 1000000)
> max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0\n
> "
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1920857#c4
Looks like the bug was introduced in 5.11-rc5, the problem doesn't
happen in rc4. As I mention in the downstream bug, I'm unable to
compile a working kernel for bisect between rc4 and rc5 to find out
the exact commit that introduced the problem, due to many messages
like this:
Feb 03 15:05:47 kernel: failed to validate module [coretemp] BTF: -22
Feb 03 15:05:47 kernel: failed to validate module [intel_powerclamp] BTF: -22
Feb 03 15:05:47 kernel: failed to validate module [irqbypass] BTF: -22
Feb 03 15:05:47 kernel: failed to validate module [intel_powerclamp] BTF: -22
Feb 03 15:05:47 kernel: failed to validate module
[x86_pkg_temp_thermal] BTF: -22
--
Chris Murphy
next prev parent reply other threads:[~2021-02-03 22:40 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 [this message]
2021-02-03 23:32 ` Andrii Nakryiko
2021-02-04 0:19 ` Chris Murphy
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='CAJCQCtRHOidM7Vps1JQSpZA14u+B5fR860FwZB=eb1wYjTpqDw@mail.gmail.com' \
--to=lists@colorremedies.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 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 NNTP newsgroup(s).