Chrome platform driver development
 help / color / mirror / Atom feed
From: Laura Nao <laura.nao@collabora.com>
To: alan.maguire@oracle.com
Cc: bpf@vger.kernel.org, chrome-platform@lists.linux.dev,
	kernel@collabora.com, laura.nao@collabora.com,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] module BTF validation failure (Error -22) on next
Date: Wed, 13 Nov 2024 10:37:03 +0100	[thread overview]
Message-ID: <20241113093703.9936-1-laura.nao@collabora.com> (raw)
In-Reply-To: <90b3b613-8665-425b-8132-5b9ac86ab616@oracle.com>

Hi Alan,

On 11/7/24 16:05, Alan Maguire wrote:
> Thanks for the report! Judging from the config, you're seeing this with
> pahole v1.24. I have seen issues like this in the past where during a
> kernel build, module BTF has been built against vmlinux BTF, and then
> something later re-triggers vmlinux BTF generation. If that re-triggered
> vmlinux BTF does not use the same type ids for types, this can result in
> mismatch errors as above since modules are referring to out-of-date type
> ids in vmlinux. That's just a preliminary guess though, we'll
> need more info to help get to the bottom of this.
> 
> A few suggestions to help debug this:
> 
> - if you have build logs, check BTF generation of vmlinux. Did it in
> fact happen twice perhaps? Even better if, if kernel CI saves logs, feel
> free to send a pointer and I'll take a look.

Thanks for the pointers!

From what I can tell in the logs, the BTF generation of vmlinux only 
occurred once. The automated build process in KernelCI generally involves 
building the kernel first, followed by the modules and other artifacts 
(such as the kselftest archive). 
The full build log can be downloaded by selecting 'build_log' from 
the dropdown menu at the top of this page:

https://kernelci-api.westus3.cloudapp.azure.com/viewer?node_id=6732f41d58937056c61734ab

I do see some warnings reported in the logs though:

WARN: resolve_btfids: unresolved symbol bpf_lsm_task_getsecid_obj
WARN: resolve_btfids: unresolved symbol bpf_lsm_current_getsecid_subj

> - can you post the vmlinux (stripped of DWARF data if possible to limit
> size) and one of the failing modules somewhere so we can analyze?
> - Failing that,
> bpftool btf dump file /path/2/vmlinux_from_build > vmlinux.raw
> and upload of the vmlinux.raw and one of the failing module .kos would help.
> 

Currently, KernelCI only retains the bzImage, not the vmlinux binary. The 
bzImage can be downloaded from the same link mentioned above by selecting 
'kernel' from the dropdown menu (modules can also be downloaded the same
way). I’ll try to replicate the build on my end and share the vmlinux 
with DWARF data stripped for convenience.

Thanks,

Laura


  reply	other threads:[~2024-11-13  9:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 16:08 [REGRESSION] module BTF validation failure (Error -22) on next Laura Nao
2024-11-07 15:05 ` Alan Maguire
2024-11-13  9:37   ` Laura Nao [this message]
2024-11-15 17:17     ` Laura Nao
2024-12-04 15:53       ` Laura Nao
2024-12-05  7:36         ` Uros Bizjak
2024-12-14  4:41           ` Cong Wang
2024-12-14 12:15             ` Alan Maguire
2024-12-16 15:19               ` Alan Maguire
2024-12-16 21:28                 ` Stephen Brennan
2024-12-17  8:02                 ` Jiri Olsa
2025-01-15 17:38                 ` Cong Wang
2025-01-16  9:51                   ` Alan Maguire
2024-12-05 10:33         ` Jiri Olsa
2024-12-05 10:35           ` Uros Bizjak
2024-12-06 12:35       ` Jiri Olsa
2024-12-10 13:55         ` [REGRESSION] module BTF validation failure (Error -22) on Laura Nao
2024-12-11 21:10           ` Jiri Olsa
2024-12-12  9:22             ` Jiri Olsa
2024-12-12 21:49               ` Stephen Brennan
2024-12-13  9:26                 ` Laura Nao
2024-12-10 20:42         ` [REGRESSION] module BTF validation failure (Error -22) on next Kumar Kartikeya Dwivedi
2024-12-05 10:01     ` Jiri Olsa

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=20241113093703.9936-1-laura.nao@collabora.com \
    --to=laura.nao@collabora.com \
    --cc=alan.maguire@oracle.com \
    --cc=bpf@vger.kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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