From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Qiliang Yuan" <odys.yuan@gmail.com>
Cc: <bpf@vger.kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <memxor@gmail.com>
Subject: Re: [PATCH bpf-next v3 00/13] bpf: Replace bpf_patch_insn_data() with a list of deferred patches
Date: Mon, 02 Nov 2026 06:40:26 +0000 [thread overview]
Message-ID: <DMKIPODYTAFW.2YX0N1TUKND78@gmail.com> (raw)
In-Reply-To: <20261102063016.652958-1-odys.yuan@gmail.com>
On Mon Nov 2, 2026 at 6:30 AM UTC, Qiliang Yuan wrote:
>> 1. Patches 12, 13: the tests need net.core.bpf_jit_harden != 2 at the
>> start.
> [...]
>> 5. Patch 6: no test has a second patch with a jump in it.
>
> By the way, I was almost done with my own v3 this morning when yours
> arrived, so I held mine back to avoid two v3s on the list. To avoid
> the same with v4: would you like me to send a v4 on top of your v3
> that fixes 1-5, or will you send it yourself? Either works for me.
Yeah. Sorry for jumping on it. My own patches were blocked on it.
Applied the set. Pls follow up.
>> In the tree today.
>> Pre-existing bugs... pick me. pick me.
>
> I'll take 10-12 and send the fixes as separate patches once the series
> lands.
Pls go ahead.
We need to accelerate kernel development 10x.
If we don't, there will be no kernel left.
next prev parent reply other threads:[~2026-11-02 6:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 1:29 [PATCH bpf-next v3 00/13] bpf: Replace bpf_patch_insn_data() with a list of deferred patches Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 01/13] bpf: Add a list of deferred instruction patches Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 02/13] bpf: Remap the verifier state through the patch list Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 03/13] bpf: Queue the rewrites of bpf_do_misc_fixups() Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 04/13] bpf: Let the patch list remove instructions Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 05/13] bpf: Move the bpf_opt_*() passes to the patch list Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 06/13] bpf: Allow patching an instruction twice through " Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 07/13] bpf: Teach the patch list to insert in front of an instruction Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 08/13] bpf: Move bpf_convert_ctx_accesses() to the patch list Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 09/13] bpf: Move the remaining verifier rewrites " Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 10/13] bpf: Blind constants through " Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 11/13] bpf: Remove the old instruction patching code Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 12/13] selftests/bpf: Test jumps around patched instructions Alexei Starovoitov
2026-11-02 1:29 ` [PATCH bpf-next v3 13/13] selftests/bpf: Test the tables that follow patched and removed instructions Alexei Starovoitov
2026-11-02 6:06 ` [PATCH bpf-next v3 00/13] bpf: Replace bpf_patch_insn_data() with a list of deferred patches Alexei Starovoitov
2026-11-02 6:30 ` Qiliang Yuan
2026-11-02 6:40 ` Alexei Starovoitov [this message]
2026-11-02 6:40 ` 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=DMKIPODYTAFW.2YX0N1TUKND78@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=odys.yuan@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