From: patchwork-bot+netdevbpf@kernel.org
To: KP Singh <kpsingh@kernel.org>
Cc: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com
Subject: Re: [PATCH bpf v3 0/2] gen_loader fixes
Date: Sat, 23 May 2026 15:00:05 +0000 [thread overview]
Message-ID: <177954840588.1595035.11316351305698858688.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260522215337.662271-1-kpsingh@kernel.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 22 May 2026 23:53:35 +0200 you wrote:
> # v2 -> v3
>
> defer fixing 32 bit.
>
> Fix off-by-one in the signed loader's cleanup jump and reject
> non-exclusive metadata maps.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/2] libbpf: fix off-by-one in emit_signature_match jump offset
https://git.kernel.org/bpf/bpf/c/7dd62566e0d1
- [bpf,v3,2/2] bpf, libbpf: reject non-exclusive metadata maps in the signed loader
(no matching commit)
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-05-23 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 21:53 [PATCH bpf v3 0/2] gen_loader fixes KP Singh
2026-05-22 21:53 ` [PATCH bpf v3 1/2] libbpf: fix off-by-one in emit_signature_match jump offset KP Singh
2026-05-22 22:41 ` bot+bpf-ci
2026-05-22 21:53 ` [PATCH bpf v3 2/2] bpf, libbpf: reject non-exclusive metadata maps in the signed loader KP Singh
2026-05-22 22:41 ` bot+bpf-ci
2026-05-23 15:12 ` Alexei Starovoitov
2026-05-23 15:00 ` 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=177954840588.1595035.11316351305698858688.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=memxor@gmail.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