BPF List
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"Jose E . Marchesi" <jose.marchesi@oracle.com>,
	kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next v3 06/24] bpf: Refactor jmp history to use dedicated spi/frame fields
Date: Mon, 11 May 2026 09:33:05 -0700	[thread overview]
Message-ID: <35a091e5-49cb-4890-a5e1-0de3a96b5d97@linux.dev> (raw)
In-Reply-To: <DIFZDSS2F9P4.9J051GNVD30G@gmail.com>



On 5/11/26 6:17 PM, Alexei Starovoitov wrote:
> On Sun May 10, 2026 at 10:33 PM PDT, Yonghong Song wrote:
>> Move stack slot index (spi) and frame number out of the flags field
>> in bpf_jmp_history_entry into dedicated bitfields. This simplifies
>> the encoding and makes room for new flags.
>>
>> Previously, spi and frame were packed into the lower 9 bits of the
>> 12-bit flags field (3 bits frame + 6 bits spi), with INSN_F_STACK_ACCESS
>> at BIT(9) and INSN_F_DST/SRC_REG_STACK at BIT(10)/BIT(11).
>> But this has no room for an INSN_F_* flag for stack arguments.
>>
>> To resolve this issue, bpf_jmp_history_entry field idx is narrowed to
>> 20 bits (sufficient for insn indices up to 1M), and the freed bits hold
>> spi (6 bits) and frame (3 bits) as dedicated struct fields. The flags
>> enum is simplified accordingly:
>>    INSN_F_STACK_ACCESS  -> BIT(0)
>>    INSN_F_DST_REG_STACK -> BIT(1)
>>    INSN_F_SRC_REG_STACK -> BIT(2)
>> which allows more room for additional INSN_F_* flags.
>>
>> bpf_push_jmp_history() now takes explicit spi and frame parameters
>> instead of encoding them into flags. The insn_stack_access_flags(),
>> insn_stack_access_spi(), and insn_stack_access_frameno() helpers are
>> removed.
>>
>> No functional change.
>>
>> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
>> ---
>>   include/linux/bpf_verifier.h | 34 ++++++++++++++--------------------
>>   kernel/bpf/backtrack.c       | 24 +++++++++---------------
>>   kernel/bpf/states.c          |  2 +-
>>   kernel/bpf/verifier.c        | 23 +++++++++++------------
>>   4 files changed, 35 insertions(+), 48 deletions(-)
>>
>> diff --git a/include/linux/bpf_verifier.h b/include/linux/bpf_verifier.h
>> index f9020a4ea005..adf00585a627 100644
>> --- a/include/linux/bpf_verifier.h
>> +++ b/include/linux/bpf_verifier.h
>> @@ -435,31 +435,22 @@ struct bpf_func_state {
>>   
>>   #define MAX_CALL_FRAMES 8
>>   
>> -/* instruction history flags, used in bpf_jmp_history_entry.flags field */
>> +/* instruction history flags, used in bpf_jmp_history_entry.flags field.
>> + * Frame number and SPI are stored in dedicated fields of bpf_jmp_history_entry.
>> + */
>>   enum {
>> -	/* instruction references stack slot through PTR_TO_STACK register;
>> -	 * we also store stack's frame number in lower 3 bits (MAX_CALL_FRAMES is 8)
>> -	 * and accessed stack slot's index in next 6 bits (MAX_BPF_STACK is 512,
>> -	 * 8 bytes per slot, so slot index (spi) is [0, 63])
>> -	 */
>> -	INSN_F_FRAMENO_MASK = 0x7, /* 3 bits */
>> -
>> -	INSN_F_SPI_MASK = 0x3f, /* 6 bits */
>> -	INSN_F_SPI_SHIFT = 3, /* shifted 3 bits to the left */
>> +	INSN_F_STACK_ACCESS = BIT(0),
>>   
>> -	INSN_F_STACK_ACCESS = BIT(9),
>> -
>> -	INSN_F_DST_REG_STACK = BIT(10), /* dst_reg is PTR_TO_STACK */
>> -	INSN_F_SRC_REG_STACK = BIT(11), /* src_reg is PTR_TO_STACK */
>> -	/* total 12 bits are used now. */
>> +	INSN_F_DST_REG_STACK = BIT(1), /* dst_reg is PTR_TO_STACK */
>> +	INSN_F_SRC_REG_STACK = BIT(2), /* src_reg is PTR_TO_STACK */
>>   };
>>   
>> -static_assert(INSN_F_FRAMENO_MASK + 1 >= MAX_CALL_FRAMES);
>> -static_assert(INSN_F_SPI_MASK + 1 >= MAX_BPF_STACK / 8);
>> -
>>   struct bpf_jmp_history_entry {
>> -	u32 idx;
>>   	/* insn idx can't be bigger than 1 million */
>> +	u32 idx : 20;
>> +	u32 frame : 3;	/* stack access frame number */
>> +	u32 spi : 6;	/* stack slot index (0..63) */
>> +	u32 : 3;
>>   	u32 prev_idx : 20;
>>   	/* special INSN_F_xxx flags */
>>   	u32 flags : 12;
> If so, should 'flags' width be reduced as well?
> We don't need to burn 12 bits after this conversion ?
> 3 bits for flags will do?

Right, the next patch will add a flag for STACK_ARG. So
total 4 bits for flags. Will make the change.


  reply	other threads:[~2026-05-11 16:33 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  5:33 [PATCH bpf-next v3 00/24] bpf: Support stack arguments for BPF functions and kfuncs Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 01/24] bpf: Convert bpf_get_spilled_reg macro to static inline function Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 02/24] bpf: Remove copy_register_state wrapper function Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 03/24] bpf: Add helper functions for r11-based stack argument insns Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 04/24] bpf: Set sub->arg_cnt earlier in btf_prepare_func_args() Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11 16:29     ` Yonghong Song
2026-05-11 17:18       ` Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 05/24] bpf: Support stack arguments for bpf functions Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11 15:46     ` Yonghong Song
2026-05-11 16:05       ` Alexei Starovoitov
2026-05-11 16:21         ` Yonghong Song
2026-05-12  4:17         ` Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 06/24] bpf: Refactor jmp history to use dedicated spi/frame fields Yonghong Song
2026-05-11 16:17   ` Alexei Starovoitov
2026-05-11 16:33     ` Yonghong Song [this message]
2026-05-11  5:33 ` [PATCH bpf-next v3 07/24] bpf: Add precision marking and backtracking for stack argument slots Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11  5:33 ` [PATCH bpf-next v3 08/24] bpf: Refactor record_call_access() to extract per-arg logic Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 09/24] bpf: Extend liveness analysis to track stack argument slots Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11 16:35     ` Yonghong Song
2026-05-11 16:34   ` Alexei Starovoitov
2026-05-11 16:40     ` Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 10/24] bpf: Reject stack arguments in non-JITed programs Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11 16:42     ` Yonghong Song
2026-05-11  5:33 ` [PATCH bpf-next v3 11/24] bpf: Prepare architecture JIT support for stack arguments Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 12/24] bpf: Enable r11 based insns Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 13/24] bpf: Support stack arguments for kfunc calls Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 14/24] bpf: Reject stack arguments if tail call reachable Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11  5:34 ` [PATCH bpf-next v3 15/24] bpf: Pass bpf_subprog_info to bpf_int_jit_compile() Yonghong Song
2026-05-11 16:38   ` Alexei Starovoitov
2026-05-11 16:47     ` Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 16/24] bpf,x86: Implement JIT support for stack arguments Yonghong Song
2026-05-11 16:39   ` Alexei Starovoitov
2026-05-11 16:47     ` Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 17/24] selftests/bpf: Add tests for BPF function " Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 18/24] selftests/bpf: Add tests for stack argument validation Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 19/24] selftests/bpf: Add BTF fixup for __naked subprog parameter names Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 20/24] selftests/bpf: Add verifier tests for stack argument validation Yonghong Song
2026-05-11  6:19   ` bot+bpf-ci
2026-05-11 16:49     ` Yonghong Song
2026-05-11  5:34 ` [PATCH bpf-next v3 21/24] selftests/bpf: Add precision backtracking test for stack arguments Yonghong Song
2026-05-11  5:35 ` [PATCH bpf-next v3 22/24] bpf, arm64: Map BPF_REG_0 to x8 instead of x7 Yonghong Song
2026-05-11  5:35 ` [PATCH bpf-next v3 23/24] bpf, arm64: Add JIT support for stack arguments Yonghong Song
2026-05-11  5:35 ` [PATCH bpf-next v3 24/24] selftests/bpf: Enable stack argument tests for arm64 Yonghong Song

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=35a091e5-49cb-4890-a5e1-0de3a96b5d97@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jose.marchesi@oracle.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    /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