public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH bpf-next] libbpf: fix internal USDT address translation logic for shared libraries
Date: Thu, 16 Jun 2022 23:30:13 +0000	[thread overview]
Message-ID: <165542221315.19703.5480668751425967007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220616055543.3285835-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 15 Jun 2022 22:55:43 -0700 you wrote:
> Perform the same virtual address to file offset translation that libbpf
> is doing for executable ELF binaries also for shared libraries.
> Currently libbpf is making a simplifying and sometimes wrong assumption
> that for shared libraries relative virtual addresses inside ELF are
> always equal to file offsets.
> 
> Unfortunately, this is not always the case with LLVM's lld linker, which
> now by default generates quite more complicated ELF segments layout.
> E.g., for liburandom_read.so from selftests/bpf, here's an excerpt from
> readelf output listing ELF segments (a.k.a. program headers):
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: fix internal USDT address translation logic for shared libraries
    https://git.kernel.org/bpf/bpf-next/c/3e6fe5ce4d48

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-06-16 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  5:55 [PATCH bpf-next] libbpf: fix internal USDT address translation logic for shared libraries Andrii Nakryiko
2022-06-16 19:59 ` Alexei Starovoitov
2022-06-16 20:38   ` Andrii Nakryiko
2022-06-16 23:30 ` patchwork-bot+netdevbpf [this message]
2022-07-20 15:32 ` Jakub Sitnicki
2022-07-20 18:32   ` Jakub Sitnicki
2022-07-28 22:04     ` 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=165542221315.19703.5480668751425967007.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox