From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH bpf-next 1/3] bpf: insn array: return proper address for non-zero offsets
Date: Wed, 14 Jan 2026 10:20:42 +0000 [thread overview]
Message-ID: <aWdt+i/ZISOBEKkP@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQ+6aByMvKttzhMWSSHM=mwiZnAd9CLVE1beHoC2o1xvrw@mail.gmail.com>
On 26/01/13 07:42PM, Alexei Starovoitov wrote:
> On Sun, Jan 11, 2026 at 7:23 AM Anton Protopopov
> <a.s.protopopov@gmail.com> wrote:
> >
> > The map_direct_value_addr() function of the instruction
> > array map incorrectly adds offset to the resulting address.
> > This is a bug, because later the resolve_pseudo_ldimm64()
> > function adds the offset. Fix it. Corresponding selftests
> > are added in a consequent commit.
> >
> > Fixes: 493d9e0d6083 ("bpf, x86: add support for indirect jumps")
> > Signed-off-by: Anton Protopopov <a.s.protopopov@gmail.com>
>
> Applied and tweaked the subject line of all 3 patches.
> Please see what I did and don't invent new prefixes.
> bpf, libbpf, selftest/bpf, bpftool, and "bpf, x86/arm64:"
> are the only categories.
> If you see others, maintainers were too lazy to do fixups.
Got it, thanks!
next prev parent reply other threads:[~2026-01-14 10:12 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 [this message]
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 ` [PATCH bpf-next 0/3] properly load insn array " patchwork-bot+netdevbpf
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=aWdt+i/ZISOBEKkP@mail.gmail.com \
--to=a.s.protopopov@gmail.com \
--cc=alexei.starovoitov@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