Chrome platform driver development
 help / color / mirror / Atom feed
From: Laura Nao <laura.nao@collabora.com>
To: olsajiri@gmail.com
Cc: alan.maguire@oracle.com, 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
Date: Tue, 10 Dec 2024 14:55:01 +0100	[thread overview]
Message-ID: <20241210135501.251505-1-laura.nao@collabora.com> (raw)
In-Reply-To: <Z1LvfndLE1t1v995@krava>

Hi Jiri,

Thanks for the feedback!

On 12/6/24 13:35, Jiri Olsa wrote:
> On Fri, Nov 15, 2024 at 06:17:12PM +0100, Laura Nao wrote:
>> On 11/13/24 10:37, Laura Nao wrote:
>>>
>>> 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.
>>>
>>
>> I managed to reproduce the issue locally and I've uploaded the
>> vmlinux[1]
>> (stripped of DWARF data) and vmlinux.raw[2] files, as well as one of
>> the
>> modules[3] and its btf data[4] extracted with:
>>
>> bpftool -B vmlinux btf dump file cros_kbd_led_backlight.ko >
>> cros_kbd_led_backlight.ko.raw
>>
>> Looking again at the logs[5], I've noticed the following is reported:
>>
>> [    0.415885] BPF: 	 type_id=115803 offset=177920 size=1152
>> [    0.416029] BPF:
>> [    0.416083] BPF: Invalid offset
>> [    0.416165] BPF:
>>
>> There are two different definitions of rcu_data in '.data..percpu',
>> one
>> is a struct and the other is an integer:
>>
>> type_id=115801 offset=177920 size=1152 (VAR 'rcu_data')
>> type_id=115803 offset=177920 size=1152 (VAR 'rcu_data')
>>
>> [115801] VAR 'rcu_data' type_id=115572, linkage=static
>> [115803] VAR 'rcu_data' type_id=1, linkage=static
>>
>> [115572] STRUCT 'rcu_data' size=1152 vlen=69
>> [1] INT 'long unsigned int' size=8 bits_offset=0 nr_bits=64
>> encoding=(none)
>>
>> I assume that's not expected, correct?
> 
> yes, that seems wrong.. but I can't reproduce with your config
> together with pahole 1.24 .. could you try with latest one?

I just tested next-20241210 with the latest pahole version (1.28 from
the master branch[1]), and the issue does not occur with this version
(I can see only one instance of rcu_data in the BTF data, as expected).

I can confirm that the same kernel revision still exhibits the issue
with pahole 1.24.

If helpful, I can also test versions between 1.24 and 1.28 to identify
which ones work.

Thanks,

Laura

[1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git

> 
> jirka
> 
>>
>> I'll dig a bit deeper and report back if I can find anything else.
>>
>> [1]
>> https://people.collabora.com/~laura.nao/dbg-btf-mismatch-next-20241113/vmlinux
>> [2]
>> https://people.collabora.com/~laura.nao/dbg-btf-mismatch-next-20241113/vmlinux.raw
>> [3]
>> https://people.collabora.com/~laura.nao/dbg-btf-mismatch-next-20241113/cros_kbd_led_backlight.ko
>> [4]
>> https://people.collabora.com/~laura.nao/dbg-btf-mismatch-next-20241113/cros_kbd_led_backlight.ko.raw
>> [5] https://pastebin.com/raw/FvvrPhAY
>>
>> Best,
>>
>> Laura
>>


  reply	other threads:[~2024-12-10 13:54 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
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         ` Laura Nao [this message]
2024-12-11 21:10           ` [REGRESSION] module BTF validation failure (Error -22) on 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=20241210135501.251505-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=olsajiri@gmail.com \
    --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