All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 0/3] Fix handling of CO-RE relos for __weak subprogs
Date: Fri, 8 Apr 2022 11:40:34 -0700	[thread overview]
Message-ID: <CAEf4BzYLYEVic8gfbL1PvhJgpKeVEs0-VM=tgU2kq7ufZPx=CQ@mail.gmail.com> (raw)
In-Reply-To: <20220408181425.2287230-1-andrii@kernel.org>

On Fri, Apr 8, 2022 at 11:14 AM Andrii Nakryiko <andrii@kernel.org> wrote:
>
> 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

"With the issue fixed", sigh...

> 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
>

  parent reply	other threads:[~2022-04-08 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 18:14 [PATCH bpf-next 0/3] Fix handling of CO-RE relos for __weak subprogs Andrii Nakryiko
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 ` Andrii Nakryiko [this message]
2022-04-08 21:09 ` [PATCH bpf-next 0/3] Fix handling of CO-RE relos for __weak subprogs 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='CAEf4BzYLYEVic8gfbL1PvhJgpKeVEs0-VM=tgU2kq7ufZPx=CQ@mail.gmail.com' \
    --to=andrii.nakryiko@gmail.com \
    --cc=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 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.