From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <a.s.protopopov@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next 0/3] properly load insn array values with offsets
Date: Wed, 14 Jan 2026 03:40:10 +0000 [thread overview]
Message-ID: <176836201004.2575016.983479775559992595.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260111153047.8388-1-a.s.protopopov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 11 Jan 2026 15:30:44 +0000 you wrote:
> As was reported by the BPF CI bot in [1] the direct address
> of an instruction array returned by map_direct_value_addr()
> is incorrect if the offset is non-zero. Fix this bug and
> add selftests.
>
> Also (commit 2), return EACCES instead of EINVAL when offsets
> aren't correct.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf: insn array: return proper address for non-zero offsets
https://git.kernel.org/bpf/bpf-next/c/e3bd7bdf5ffe
- [bpf-next,2/3] bpf: insn array: return EACCES for incorrect map access
https://git.kernel.org/bpf/bpf-next/c/7e525860e725
- [bpf-next,3/3] selftests/bpf: add tests for loading map values with offsets
https://git.kernel.org/bpf/bpf-next/c/c656807675e0
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-01-14 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 15:30 [PATCH bpf-next 0/3] properly load insn array values with offsets Anton Protopopov
2026-01-11 15:30 ` [PATCH bpf-next 1/3] bpf: insn array: return proper address for non-zero offsets Anton Protopopov
2026-01-12 17:05 ` Emil Tsalapatis
2026-01-14 3:42 ` Alexei Starovoitov
2026-01-14 10:20 ` Anton Protopopov
2026-01-11 15:30 ` [PATCH bpf-next 2/3] bpf: insn array: return EACCES for incorrect map access Anton Protopopov
2026-01-12 17:12 ` Emil Tsalapatis
2026-01-12 18:45 ` Anton Protopopov
2026-01-12 19:18 ` Emil Tsalapatis
2026-01-11 15:30 ` [PATCH bpf-next 3/3] selftests/bpf: add tests for loading map values with offsets Anton Protopopov
2026-01-14 3:40 ` 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=176836201004.2575016.983479775559992595.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox