BPF List
 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,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] libbpf: don't adjust USDT semaphore address if .stapsdt.base addr is missing
Date: Mon, 25 Nov 2024 22:20:32 +0000	[thread overview]
Message-ID: <173257323249.4055688.7017818062668183425.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241121224558.796110-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 21 Nov 2024 14:45:58 -0800 you wrote:
> USDT ELF note optionally can record an offset of .stapsdt.base, which is
> used to make adjustments to USDT target attach address. Currently,
> libbpf will do this address adjustment unconditionally if it finds
> .stapsdt.base ELF section in target binary. But there is a corner case
> where .stapsdt.base ELF section is present, but specific USDT note
> doesn't reference it. In such case, libbpf will basically just add base
> address and end up with absolutely incorrect USDT target address.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: don't adjust USDT semaphore address if .stapsdt.base addr is missing
    https://git.kernel.org/bpf/bpf-next/c/d00058e676a9

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



      parent reply	other threads:[~2024-11-25 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 22:45 [PATCH bpf-next] libbpf: don't adjust USDT semaphore address if .stapsdt.base addr is missing Andrii Nakryiko
2024-11-22 16:20 ` Jiri Olsa
2024-11-25 22:20 ` patchwork-bot+netdevbpf [this message]

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=173257323249.4055688.7017818062668183425.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@meta.com \
    --cc=martin.lau@kernel.org \
    /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