All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, Song Liu <song@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Hao Luo <haoluo@google.com>, Ian Rogers <irogers@google.com>
Subject: [HELP] failed to resolve CO-RE relocation
Date: Wed, 26 Apr 2023 17:14:25 -0700	[thread overview]
Message-ID: <20230427001425.563232-1-namhyung@kernel.org> (raw)

Hello,

I'm having a problem of loading perf lock contention BPF program [1]
on old kernels.  It has collect_lock_syms() to get the address of each
CPU's run-queue lock.  The kernel 5.14 changed the name of the field
so there's bpf_core_field_exists to check the name like below.

	if (bpf_core_field_exists(rq_new->__lock))
		lock_addr = (__u64)&rq_new->__lock;
	else
		lock_addr = (__u64)&rq_old->lock;

Note that I've applied a patch [2] to fix an issue with this code.

It works fine on my machine (with a newer kernel), but failed on the
old kernels.  I guess it'd go to the else part without a problem but
it didn't for some reason.

Then I change the code to check the rq_old first.  It works well on
the old kernels but fails on newer kernels.. :(

    libbpf: prog 'collect_lock_syms': BPF program load failed: Invalid argument
    libbpf: prog 'collect_lock_syms': -- BEGIN PROG LOAD LOG --
    reg type unsupported for arg#0 function collect_lock_syms#380
    0: R1=ctx(off=0,imm=0) R10=fp0
    ; int BPF_PROG(collect_lock_syms)
    0: (b7) r6 = 0                        ; R6_w=0
    1: (b7) r7 = 0                        ; R7_w=0
    2: (b7) r9 = 1                        ; R9_w=1
    3: <invalid CO-RE relocation>
    failed to resolve CO-RE relocation <byte_off> [381] struct rq___old.lock (0:0 @ offset 0)
    processed 4 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0

I'm curious what went wrong with this.  I guess it's supposed to work
on any kernel verions by definition.  Not sure the compiler generated
a wrong reloc or something.  Maybe I just made silly mistakes..

Do you see anything wrong?  Any hints to debug this issue?

Thanks,
Namhyung


[1] file://linux/tools/perf/util/bpf_skel/lock_contention.bpf.c
[2] https://lore.kernel.org/lkml/20230423215650.287812-1-namhyung@kernel.org/

             reply	other threads:[~2023-04-27  0:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  0:14 Namhyung Kim [this message]
2023-04-27  1:19 ` [HELP] failed to resolve CO-RE relocation Andrii Nakryiko
2023-04-27  2:21   ` Namhyung Kim
2023-04-27  4:19     ` Hengqi Chen
2023-04-27  4:27       ` Namhyung Kim
2023-04-27  4:26     ` Andrii Nakryiko
2023-04-27  4:53       ` Namhyung Kim
2023-04-27 22:15         ` Andrii Nakryiko
2023-04-27 23:27           ` Namhyung Kim
2023-04-27 23:38             ` Andrii Nakryiko

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=20230427001425.563232-1-namhyung@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=song@kernel.org \
    --cc=yhs@fb.com \
    /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.