All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Anton Protopopov <aspsk@isovalent.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Quentin Monnet <qmo@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH v8 bpf-next 01/11] bpf, x86: add new map type: instructions array
Date: Fri, 31 Oct 2025 07:23:13 +0000	[thread overview]
Message-ID: <aQRj4bxjbrECVIb9@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQL1nznRsfdSgFPxSf1Rdhq7hpQMcmT7BKaRn9KHwD=P6A@mail.gmail.com>

On 25/10/30 03:50PM, Alexei Starovoitov wrote:
> On Tue, Oct 28, 2025 at 7:15 AM Anton Protopopov
> <a.s.protopopov@gmail.com> wrote:
> >                 }
> > +
> > +               bpf_prog_update_insn_ptrs(prog, addrs, image);
> > +
> 
> I suspect there is off-by-1 bug somewhere in bpf_prog_update_insn_ptrs() math,
> since addrs[0] points to function prologue.
> addrs[1] is the offset of the first bpf insn.
> See how it's called in other place:
>    bpf_prog_fill_jited_linfo(prog, addrs + 1);

So all the maps I have in all selftests tests point to a wrong ip for
every goto, and still work?

In fact, addrs[0] points to right after the prologue, see how it is
initialized in do_jit:

  addrs[0] = proglen;

here proglen is the length of prologue. The loop in do_jit startrs
with i=1, but all addrs are referenced with i-1:

    case BPF_JMP | BPF_CALL: {
            u8 *ip = image + addrs[i - 1];

The bpf_prog_fill_jited_linfo internally also does the -1 thingy:

    insn_to_jit_off[linfo[i].insn_off - insn_start - 1];

> pw-bot: cr

^ will send v9 in a few days with minor fixes pointed by Eduard and Andrii

  reply	other threads:[~2025-10-31  7:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 14:20 [PATCH v8 bpf-next 00/11] BPF indirect jumps Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 01/11] bpf, x86: add new map type: instructions array Anton Protopopov
2025-10-30 22:50   ` Alexei Starovoitov
2025-10-31  7:23     ` Anton Protopopov [this message]
2025-10-31 15:04       ` Alexei Starovoitov
2025-10-31 15:20         ` Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 02/11] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 03/11] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 04/11] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 05/11] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 06/11] bpf, x86: add support for indirect jumps Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 07/11] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 08/11] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-10-29 21:31   ` Eduard Zingerman
2025-11-03  4:15     ` Yonghong Song
2025-10-30 21:00   ` Andrii Nakryiko
2025-10-31  7:30     ` Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 09/11] bpftool: Recognize insn_array map type Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 10/11] selftests/bpf: add new verifier_gotox test Anton Protopopov
2025-10-28 14:45   ` bot+bpf-ci
2025-10-28 15:05     ` Anton Protopopov
2025-10-28 14:20 ` [PATCH v8 bpf-next 11/11] selftests/bpf: add C-level selftests for indirect jumps Anton Protopopov
2025-10-29 21:49   ` Eduard Zingerman
2025-10-30  7:46     ` Anton Protopopov

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=aQRj4bxjbrECVIb9@mail.gmail.com \
    --to=a.s.protopopov@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=qmo@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.