From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/3] Fix handling of CO-RE relos for __weak subprogs
Date: Fri, 8 Apr 2022 11:14:22 -0700 [thread overview]
Message-ID: <20220408181425.2287230-1-andrii@kernel.org> (raw)
Fix the issue accidentally discovered during libbpf USDT support testing.
Libbpf overzealously complained about CO-RE relocations belonging to the code
of a __weak subprog that got overriden by another instance of that function.
Fix the issue fixed, return back to __weak __hidden annotation for USDT
BPF-side APIs.
And add CO-RE relos to linked_funcs selftest to ensure such combo keeps
working going forward.
Andrii Nakryiko (3):
libbpf: don't error out on CO-RE relos for overriden weak subprogs
libbpf: use weak hidden modifier for USDT BPF-side API functions
selftests/bpf: add CO-RE relos into linked_funcs selftests
tools/lib/bpf/libbpf.c | 15 +++++++++++----
tools/lib/bpf/usdt.bpf.h | 6 +++---
tools/testing/selftests/bpf/progs/linked_funcs1.c | 8 ++++++++
tools/testing/selftests/bpf/progs/linked_funcs2.c | 8 ++++++++
4 files changed, 30 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-08 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 18:14 Andrii Nakryiko [this message]
2022-04-08 18:14 ` [PATCH bpf-next 1/3] libbpf: don't error out on CO-RE relos for overriden weak subprogs Andrii Nakryiko
2022-04-08 18:14 ` [PATCH bpf-next 2/3] libbpf: use weak hidden modifier for USDT BPF-side API functions Andrii Nakryiko
2022-04-08 18:14 ` [PATCH bpf-next 3/3] selftests/bpf: add CO-RE relos into linked_funcs selftests Andrii Nakryiko
2022-04-08 18:40 ` [PATCH bpf-next 0/3] Fix handling of CO-RE relos for __weak subprogs Andrii Nakryiko
2022-04-08 21:09 ` patchwork-bot+netdevbpf
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=20220408181425.2287230-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox