From: patchwork-bot+netdevbpf@kernel.org
To: Luis Vieira <luisflavieira@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: Fix cleanup on invalid CO-RE relocation offsets
Date: Wed, 30 Sep 2026 09:50:04 +0000 [thread overview]
Message-ID: <179076180483.1366309.473741544012834911.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929-libbpf-core-relo-cleanup-v1-1-c9cd0b5775a9@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 29 Sep 2026 22:56:12 -0300 you wrote:
> bpf_object__relocate_core() allocates a CO-RE candidate cache before
> processing relocation records. Two instruction offset validation
> failures return -EINVAL directly instead of going through the common
> cleanup path.
>
> These checks were moved into bpf_object__relocate_core() when
> bpf_core_apply_relo() was split, preserving direct returns that were
> safe in the previous helper but now bypass cleanup.
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: Fix cleanup on invalid CO-RE relocation offsets
https://git.kernel.org/bpf/bpf-next/c/acff58e30517
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-30 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 1:56 [PATCH bpf-next] libbpf: Fix cleanup on invalid CO-RE relocation offsets Luis Vieira
2026-09-30 9:50 ` 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=179076180483.1366309.473741544012834911.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisflavieira@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.