bpf: Support new insns from cpu v4
Subsystems (9)
Yonghong Song
reviewerv5 cover bpf: Support new insns from cpu v4
In previous discussion ([1]), it is agreed that we should introduce cpu version 4 (llvm flag -mcpu=v4) which contains some instructions which can simplify code, make code easier to understand, fix the existing problem, or simply for feature completeness. More specifically, the following new insns are proposed:
. sign extended load
. sign extended mov
. bswap
. signed div/mod
. ja with 32-bit offset
This patch set added kernel support for insns proposed in [1] except BPF_ST which already has full kernel support. Beside the above proposed insns, LLVM will generate BPF_ST insn as well under -mcpu=v4. The llvm patch ([2]) has been merged into llvm-project 'main' branch.
The patchset implements interpreter, jit and verifier support for these new insns.
For this patch set, I tested cpu v2/v3/v4 and the selftests are all passed. I also tested selftests introduced in this patch set with additional changes beside normal jit testing (bpf_jit_enable = 1 and bpf_jit_harden = 0)
- bpf_jit_enable = 0
- bpf_jit_enable = 1 and bpf_jit_harden = 1
and both testing passed.
[1] https://lore.kernel.org/bpf/[email protected]/
[2] https://reviews.llvm.org/D144829
Changelogs:
v4 -> v5:
. for v4, patch 8/17 missed in mailing list and patchwork, so resend. . rebase on top of master
v3 -> v4:
. some minor asm syntax adjustment based on llvm change. . add clang version and target arch guard for new tests
so they can still compile with old llvm compilers.
. some changes to the bpf doc.
v2 -> v3:
. add missed disasm change from v2.
. handle signed load of ctx fields properly.
. fix some interpreter sdiv/smod error when bpf_jit_enable = 0. . fix some verifier range bounding errors.
. add more C tests.
RFCv1 -> v2:
. add more verifier supports for signed extend load and mov insns. . rename some insn names to be more consistent with intel practice. . add cpuv4 test runner for test progs.
. add more unit and C tests.
. add documentation.
Yonghong Song (17):
bpf: Support new sign-extension load insns
bpf: Support new sign-extension mov insns
bpf: Handle sign-extenstin ctx member accesses
bpf: Support new unconditional bswap instruction
bpf: Support new signed div/mod instructions.
bpf: Fix jit blinding with new sdiv/smov insns
bpf: Support new 32bit offset jmp instruction
bpf: Add kernel/bpftool asm support for new instructions selftests/bpf: Fix a test_verifier failure selftests/bpf: Add a cpuv4 test runner for cpu=v4 testing selftests/bpf: Add unit tests for new sign-extension load insns selftests/bpf: Add unit tests for new sign-extension mov insns selftests/bpf: Add unit tests for new bswap insns selftests/bpf: Add unit tests for new sdiv/smod insns selftests/bpf: Add unit tests for new gotol insn selftests/bpf: Test ldsx with more complex cases docs/bpf: Add documentation for new instructions
Documentation/bpf/bpf_design_QA.rst | 5 - .../bpf/standardization/instruction-set.rst | 115 ++- arch/x86/net/bpf_jit_comp.c | 141 +++- include/linux/filter.h | 17 +- include/uapi/linux/bpf.h | 1 + kernel/bpf/core.c | 196 ++++- kernel/bpf/disasm.c | 57 +- kernel/bpf/verifier.c | 348 ++++++-- tools/include/uapi/linux/bpf.h | 1 + tools/testing/selftests/bpf/.gitignore | 2 + tools/testing/selftests/bpf/Makefile | 28 +- .../selftests/bpf/bpf_testmod/bpf_testmod.c | 9 +- .../selftests/bpf/prog_tests/test_ldsx_insn.c | 139 ++++ .../selftests/bpf/prog_tests/verifier.c | 10 + .../selftests/bpf/progs/test_ldsx_insn.c | 118 +++ .../selftests/bpf/progs/verifier_bswap.c | 59 ++ .../selftests/bpf/progs/verifier_gotol.c | 44 + .../selftests/bpf/progs/verifier_ldsx.c | 131 +++ .../selftests/bpf/progs/verifier_movsx.c | 213 +++++ .../selftests/bpf/progs/verifier_sdiv.c | 781 ++++++++++++++++++ .../selftests/bpf/verifier/basic_instr.c | 6 +- 21 files changed, 2251 insertions(+), 170 deletions(-) create mode 100644 tools/testing/selftests/bpf/prog_tests/test_ldsx_insn.c create mode 100644 tools/testing/selftests/bpf/progs/test_ldsx_insn.c create mode 100644 tools/testing/selftests/bpf/progs/verifier_bswap.c create mode 100644 tools/testing/selftests/bpf/progs/verifier_gotol.c create mode 100644 tools/testing/selftests/bpf/progs/verifier_ldsx.c create mode 100644 tools/testing/selftests/bpf/progs/verifier_movsx.c create mode 100644 tools/testing/selftests/bpf/progs/verifier_sdiv.c
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 1/17 bpf: Support new sign-extension load insns
Add interpreter/jit support for new sign-extension load insns which adds a new mode (BPF_MEMSX).
Also add verifier support to recognize these insns and to do proper verification with new insns. In verifier, besides to deduce proper bounds for the dst_reg, probed memory access is also properly handled.
--- arch/x86/net/bpf_jit_comp.c | 42 +++++++++- include/linux/filter.h | 3 + include/uapi/linux/bpf.h | 1 + kernel/bpf/core.c | 21 +++++ kernel/bpf/verifier.c | 140 +++++++++++++++++++++++++++------ tools/include/uapi/linux/bpf.h | 1 + 6 files changed, 181 insertions(+), 27 deletions(-)
arch/x86/net/bpf_jit_comp.c +39 -3
@@ -779,6 +779,29 @@ static void emit_ldx(u8 **pprog, u32 size, u32 dst_reg, u32 src_reg, int off) *pprog = prog; } +/* LDSX: dst_reg = *(s8*)(src_reg + off) */ +static void emit_ldsx (u8 **pprog,u32 size,u32 dst_reg,u32 src_reg,int off) +{ +u8 *prog = *pprog; + +switch (size) { +case BPF_B : +/* Emit 'movsx rax, byte ptr [rax + off]' */ +EMIT3 (add_2mod (0x48 , src_reg, dst_reg),0x0F ,0xBE ); +break ; +case BPF_H : +/* Emit 'movsx rax, word ptr [rax + off]' */ +EMIT3 (add_2mod (0x48 , src_reg, dst_reg),0x0F ,0xBF ); +break ; +case BPF_W : +/* Emit 'movsx rax, dword ptr [rax+0x14]' */ +EMIT2 (add_2mod (0x48 , src_reg, dst_reg),0x63 ); +break ; + } +emit_insn_suffix (&prog, src_reg, dst_reg, off); + *pprog = prog; +} +/* STX: *(u8*)(dst_reg + off) = src_reg */ static void emit_stx (u8 **pprog,u32 size,u32 dst_reg,u32 src_reg,int off) {
@@ -1370,9 +1393,17 @@ st: if (is_imm8(insn->off))case BPF_LDX |BPF_PROBE_MEM |BPF_W :case BPF_LDX |BPF_MEM |BPF_DW :case BPF_LDX |BPF_PROBE_MEM |BPF_DW : +/* LDXS: dst_reg = *(s8*)(src_reg + off) */ +case BPF_LDX |BPF_MEMSX |BPF_B : +case BPF_LDX |BPF_MEMSX |BPF_H : +case BPF_LDX |BPF_MEMSX |BPF_W : +case BPF_LDX |BPF_PROBE_MEMSX |BPF_B : +case BPF_LDX |BPF_PROBE_MEMSX |BPF_H : +case BPF_LDX |BPF_PROBE_MEMSX |BPF_W : insn_off = insn->off; -if (BPF_MODE (insn->code) ==BPF_PROBE_MEM ) { +if (BPF_MODE (insn->code) ==BPF_PROBE_MEM || +BPF_MODE (insn->code) ==BPF_PROBE_MEMSX ) {/* Conservatively check that src_reg + insn->off is a kernel address: * src_reg + insn->off >= TASK_SIZE_MAX + PAGE_SIZE * src_reg is used as scratch for src_reg += insn->off and restored
@@ -1415,8 +1446,13 @@ st: if (is_imm8(insn->off)) start_of_ldx = prog; end_of_jmp[-1 ] = start_of_ldx - end_of_jmp; } -emit_ldx (&prog,BPF_SIZE (insn->code), dst_reg, src_reg, insn_off); -if (BPF_MODE (insn->code) ==BPF_PROBE_MEM ) { +if (BPF_MODE (insn->code) ==BPF_PROBE_MEMSX || +BPF_MODE (insn->code) ==BPF_MEMSX ) +emit_ldsx (&prog,BPF_SIZE (insn->code), dst_reg, src_reg, insn_off); +else +emit_ldx (&prog,BPF_SIZE (insn->code), dst_reg, src_reg, insn_off); +if (BPF_MODE (insn->code) ==BPF_PROBE_MEM || +BPF_MODE (insn->code) ==BPF_PROBE_MEMSX ) {struct exception_table_entry *ex;u8 *_insn = image + proglen + (start_of_ldx - temp);s64 delta;
include/linux/filter.h +3 -0
@@ -69,6 +69,9 @@ struct ctl_table_header;/* unused opcode to mark special load instruction. Same as BPF_ABS */ #define BPF_PROBE_MEM 0x20 +/* unused opcode to mark special ldsx instruction. Same as BPF_IND */ +#define BPF_PROBE_MEMSX 0x40 +/* unused opcode to mark call to interpreter with arguments */ #define BPF_CALL_ARGS 0xe0
include/uapi/linux/bpf.h +1 -0
@@ -19,6 +19,7 @@/* ld/ldx fields */ #define BPF_DW 0x18/* double word (64-bit) */ +#define BPF_MEMSX 0x80/* load with sign extension */ #define BPF_ATOMIC 0xc0/* atomic memory ops - op type in immediate */ #define BPF_XADD 0xc0/* exclusive add - legacy name */
kernel/bpf/core.c +21 -0
@@ -1610,6 +1610,9 @@ EXPORT_SYMBOL_GPL(__bpf_call_base);INSN_3 (LDX ,MEM ,H ), \INSN_3 (LDX ,MEM ,W ), \INSN_3 (LDX ,MEM ,DW ), \ +INSN_3 (LDX ,MEMSX ,B ), \ +INSN_3 (LDX ,MEMSX ,H ), \ +INSN_3 (LDX ,MEMSX ,W ), \/* Immediate based. */ \INSN_3 (LD ,IMM ,DW )
@@ -1666,6 +1669,9 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) [BPF_LDX | BPF_PROBE_MEM | BPF_H] = &&LDX_PROBE_MEM_H, [BPF_LDX | BPF_PROBE_MEM | BPF_W] = &&LDX_PROBE_MEM_W, [BPF_LDX | BPF_PROBE_MEM | BPF_DW] = &&LDX_PROBE_MEM_DW, + [BPF_LDX | BPF_PROBE_MEMSX | BPF_B] = &&LDX_PROBE_MEMSX_B, + [BPF_LDX | BPF_PROBE_MEMSX | BPF_H] = &&LDX_PROBE_MEMSX_H, + [BPF_LDX | BPF_PROBE_MEMSX | BPF_W] = &&LDX_PROBE_MEMSX_W, };#undef BPF_INSN_3_LBL#undef BPF_INSN_2_LBL
@@ -1942,6 +1948,21 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) LDST(DW, u64)#undef LDST +#define LDSX (SIZEOP ,SIZE ) \ + LDX_MEMSX_##SIZEOP: \ + DST = *(SIZE *)(unsigned long) (SRC + insn->off); \ + CONT; \ + LDX_PROBE_MEMSX_##SIZEOP: \ + bpf_probe_read_kernel(&DST, sizeof(SIZE), \ + (const void *)(long) (SRC + insn->off)); \ + DST = *((SIZE *)&DST); \ + CONT; + + LDSX(B, s8) + LDSX(H, s16) + LDSX(W, s32) +#undef LDSX +#define ATOMIC_ALU_OP (BOP ,KOP ) \ case BOP: \ if (BPF_SIZE(insn->code) == BPF_W) \
kernel/bpf/verifier.c +116 -24
266 lines not on this page · raw message
tools/include/uapi/linux/bpf.h +1 -0
@@ -19,6 +19,7 @@/* ld/ldx fields */ #define BPF_DW 0x18/* double word (64-bit) */ +#define BPF_MEMSX 0x80/* load with sign extension */ #define BPF_ATOMIC 0xc0/* atomic memory ops - op type in immediate */ #define BPF_XADD 0xc0/* exclusive add - legacy name */
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 2/17 bpf: Support new sign-extension mov insns
In reply to Yonghong SongAdd interpreter/jit support for new sign-extension mov insns. The original 'MOV' insn is extended to support reg-to-reg signed version for both ALU and ALU64 operations. For ALU mode, the insn->off value of 8 or 16 indicates sign-extension from 8- or 16-bit value to 32-bit value. For ALU64 mode, the insn->off value of 8/16/32 indicates sign-extension from 8-, 16- or 32-bit value to 64-bit value.
--- arch/x86/net/bpf_jit_comp.c | 43 +++++++++- kernel/bpf/core.c | 28 ++++++- kernel/bpf/verifier.c | 157 ++++++++++++++++++++++++++++++------ 3 files changed, 197 insertions(+), 31 deletions(-)
arch/x86/net/bpf_jit_comp.c +40 -3
@@ -701,6 +701,38 @@ static void emit_mov_reg(u8 **pprog, bool is64, u32 dst_reg, u32 src_reg) *pprog = prog; } +static void emit_movsx_reg (u8 **pprog,int num_bits,bool is64,u32 dst_reg, +u32 src_reg) +{ +u8 *prog = *pprog; + +if (is64) { +/* movs[b,w,l]q dst, src */ +if (num_bits ==8 ) +EMIT4 (add_2mod (0x48 , src_reg, dst_reg),0x0f ,0xbe , +add_2reg (0xC0 , src_reg, dst_reg)); +else if (num_bits ==16 ) +EMIT4 (add_2mod (0x48 , src_reg, dst_reg),0x0f ,0xbf , +add_2reg (0xC0 , src_reg, dst_reg)); +else if (num_bits ==32 ) +EMIT3 (add_2mod (0x48 , src_reg, dst_reg),0x63 , +add_2reg (0xC0 , src_reg, dst_reg)); + }else { +/* movs[b,w]l dst, src */ +if (num_bits ==8 ) { +EMIT4 (add_2mod (0x40 , src_reg, dst_reg),0x0f ,0xbe , +add_2reg (0xC0 , src_reg, dst_reg)); + }else if (num_bits ==16 ) { +if (is_ereg (dst_reg) ||is_ereg (src_reg)) +EMIT1 (add_2mod (0x40 , src_reg, dst_reg)); +EMIT3 (add_2mod (0x0f , src_reg, dst_reg),0xbf , +add_2reg (0xC0 , src_reg, dst_reg)); + } + } + + *pprog = prog; +} +/* Emit the suffix (ModR/M etc) for addressing *(ptr_reg + off) and val_reg */ static void emit_insn_suffix (u8 **pprog,u32 ptr_reg,u32 val_reg,int off) {
@@ -1051,9 +1083,14 @@ static int do_jit(struct bpf_prog *bpf_prog, int *addrs, u8 *image, u8 *rw_imagecase BPF_ALU64 |BPF_MOV |BPF_X :case BPF_ALU |BPF_MOV |BPF_X : -emit_mov_reg (&prog, -BPF_CLASS (insn->code) ==BPF_ALU64 , - dst_reg, src_reg); +if (insn->off ==0 ) +emit_mov_reg (&prog, +BPF_CLASS (insn->code) ==BPF_ALU64 , + dst_reg, src_reg); +else +emit_movsx_reg (&prog, insn->off, +BPF_CLASS (insn->code) ==BPF_ALU64 , + dst_reg, src_reg);break ;/* neg dst */
kernel/bpf/core.c +26 -2
@@ -61,6 +61,7 @@#define AX regs[BPF_REG_AX]#define ARG1 regs[BPF_REG_ARG1]#define CTX regs[BPF_REG_CTX] +#define OFF insn->off#define IMM insn->immstruct bpf_mem_alloc bpf_global_ma;
@@ -1739,13 +1740,36 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)DST = -DST ;CONT ; ALU_MOV_X: -DST = (u32 )SRC ; +switch (OFF ) { +case 0 : +DST = (u32 )SRC ; +break ; +case 8 : +DST = (u32 )(s8 )SRC ; +break ; +case 16 : +DST = (u32 )(s16 )SRC ; +break ; + }CONT ; ALU_MOV_K:DST = (u32 )IMM ;CONT ; ALU64_MOV_X: -DST =SRC ; +switch (OFF ) { +case 0 : +DST =SRC ; +break ; +case 8 : +DST = (s8 )SRC ; +break ; +case 16 : +DST = (s16 )SRC ; +break ; +case 32 : +DST = (s32 )SRC ; +break ; + }CONT ; ALU64_MOV_K:DST =IMM ;
kernel/bpf/verifier.c +131 -26
192 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 3/17 bpf: Handle sign-extenstin ctx member accesses
In reply to Yonghong SongCurrently, if user accesses a ctx member with signed types, the compiler will generate an unsigned load followed by necessary left and right shifts.
With the introduction of sign-extension load, compiler may just emit a ldsx insn instead. Let us do a final movsx sign extension to the final unsigned ctx load result to satisfy original sign extension requirement.
--- kernel/bpf/verifier.c | 6 ++++++ 1 file changed, 6 insertions(+)
kernel/bpf/verifier.c +6 -0
@@ -17716,6 +17716,7 @@ static int convert_ctx_accesses(struct bpf_verifier_env *env)for (i =0 ; i < insn_cnt; i++, insn++) {bpf_convert_ctx_access_t convert_ctx_access; +u8 mode; if (insn->code == (BPF_LDX | BPF_MEM | BPF_B) || insn->code == (BPF_LDX | BPF_MEM | BPF_H) ||
@@ -17797,6 +17798,7 @@ static int convert_ctx_accesses(struct bpf_verifier_env *env) ctx_field_size = env->insn_aux_data[i + delta].ctx_field_size; size =BPF_LDST_BYTES (insn); + mode =BPF_MODE (insn->code);/* If the read access is a narrower load of the field, * convert to a 4/8-byte load, to minimum program type specific
@@ -17856,6 +17858,10 @@ static int convert_ctx_accesses(struct bpf_verifier_env *env) (1ULL << size * 8) - 1); } } +if (mode ==BPF_MEMSX ) + insn_buf[cnt++] =BPF_RAW_INSN (BPF_ALU64 |BPF_MOV |BPF_X , + insn->dst_reg, insn->dst_reg, + size *8 ,0 ); new_prog =bpf_patch_insn_data (env, i + delta, insn_buf, cnt);if (!new_prog)
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 4/17 bpf: Support new unconditional bswap instruction
In reply to Yonghong SongThe existing 'be' and 'le' insns will do conditional bswap depends on host endianness. This patch implements unconditional bswap insns.
--- arch/x86/net/bpf_jit_comp.c | 1 + kernel/bpf/core.c | 14 ++++++++++++++ kernel/bpf/verifier.c | 7 +++++-- 3 files changed, 20 insertions(+), 2 deletions(-)
arch/x86/net/bpf_jit_comp.c +1 -0
@@ -1322,6 +1322,7 @@ static int do_jit(struct bpf_prog *bpf_prog, int *addrs, u8 *image, u8 *rw_imagebreak ;case BPF_ALU |BPF_END |BPF_FROM_BE : +case BPF_ALU64 |BPF_END |BPF_FROM_LE :switch (imm32) {case 16 :/* Emit 'ror %ax, 8' to swap lower 2 bytes */
kernel/bpf/core.c +14 -0
@@ -1524,6 +1524,7 @@ EXPORT_SYMBOL_GPL(__bpf_call_base);INSN_3 (ALU64 ,DIV ,X ), \INSN_3 (ALU64 ,MOD ,X ), \INSN_2 (ALU64 ,NEG ), \ +INSN_3 (ALU64 ,END ,TO_LE ), \/* Immediate based. */ \INSN_3 (ALU64 ,ADD ,K ), \ INSN_3(ALU64, SUB, K), \
@@ -1848,6 +1849,19 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)break ; }CONT ; + ALU64_END_TO_LE: +switch (IMM ) { +case 16 : +DST = (__force u16 )__swab16 (DST ); +break ; +case 32 : +DST = (__force u32 )__swab32 (DST ); +break ; +case 64 : +DST = (__force u64 )__swab64 (DST ); +break ; + } +CONT ;/* CALL */ JMP_CALL:
kernel/bpf/verifier.c +5 -2
@@ -3012,8 +3012,10 @@ static bool is_reg64(struct bpf_verifier_env *env, struct bpf_insn *insn, } } +if (class ==BPF_ALU64 && op ==BPF_END && (insn->imm ==16 || insn->imm ==32 )) +return false; +if (class ==BPF_ALU64 || class ==BPF_JMP || -/* BPF_END always use BPF_ALU class. */ (class ==BPF_ALU && op ==BPF_END && insn->imm ==64 ))return true;
@@ -13076,7 +13078,8 @@ static int check_alu_op(struct bpf_verifier_env *env, struct bpf_insn *insn) }else {if (insn->src_reg !=BPF_REG_0 || insn->off !=0 || (insn->imm !=16 && insn->imm !=32 && insn->imm !=64 ) || -BPF_CLASS (insn->code) ==BPF_ALU64 ) { + (BPF_CLASS (insn->code) ==BPF_ALU64 && +BPF_SRC (insn->code) !=BPF_TO_LE )) {verbose (env,"BPF_END uses reserved fields\n" );return -EINVAL ; }
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 5/17 bpf: Support new signed div/mod instructions.
In reply to Yonghong SongAdd interpreter/jit support for new signed div/mod insns. The new signed div/mod instructions are encoded with unsigned div/mod instructions plus insn->off == 1. Also add basic verifier support to ensure new insns get accepted.
--- arch/x86/net/bpf_jit_comp.c | 27 ++++++--- kernel/bpf/core.c | 110 ++++++++++++++++++++++++++++++------ kernel/bpf/verifier.c | 6 +- 3 files changed, 117 insertions(+), 26 deletions(-)
arch/x86/net/bpf_jit_comp.c +19 -8
@@ -1194,15 +1194,26 @@ static int do_jit(struct bpf_prog *bpf_prog, int *addrs, u8 *image, u8 *rw_image/* mov rax, dst_reg */ emit_mov_reg (&prog, is64,BPF_REG_0 , dst_reg); -/* -* xor edx, edx -* equivalent to 'xor rdx, rdx', but one byte less -*/ -EMIT2 (0x31 ,0xd2 ); +if (insn->off ==0 ) { +/* +* xor edx, edx +* equivalent to 'xor rdx, rdx', but one byte less +*/ +EMIT2 (0x31 ,0xd2 ); -/* div src_reg */ -maybe_emit_1mod (&prog, src_reg, is64); -EMIT2 (0xF7 ,add_1reg (0xF0 , src_reg)); +/* div src_reg */ +maybe_emit_1mod (&prog, src_reg, is64); +EMIT2 (0xF7 ,add_1reg (0xF0 , src_reg)); + }else { +if (BPF_CLASS (insn->code) ==BPF_ALU ) +EMIT1 (0x99 );/* cdq */ +else +EMIT2 (0x48 ,0x99 );/* cqo */ + +/* idiv src_reg */ +maybe_emit_1mod (&prog, src_reg, is64); +EMIT2 (0xF7 ,add_1reg (0xF8 , src_reg)); + }if (BPF_OP (insn->code) ==BPF_MOD && dst_reg !=BPF_REG_3 )
kernel/bpf/core.c +94 -16
130 lines not on this page · raw message
kernel/bpf/verifier.c +4 -2
@@ -13237,7 +13237,8 @@ static int check_alu_op(struct bpf_verifier_env *env, struct bpf_insn *insn) }else {/* all other ALU ops: and, sub, xor, add, ... */ if (BPF_SRC (insn->code) ==BPF_X ) { -if (insn->imm !=0 || insn->off !=0 ) { +if (insn->imm !=0 || insn->off >1 || + (insn->off ==1 && opcode !=BPF_MOD && opcode !=BPF_DIV )) {verbose (env,"BPF_ALU uses reserved fields\n" );return -EINVAL ; }
@@ -13246,7 +13247,8 @@ static int check_alu_op(struct bpf_verifier_env *env, struct bpf_insn *insn)if (err)return err; }else { -if (insn->src_reg !=BPF_REG_0 || insn->off !=0 ) { +if (insn->src_reg !=BPF_REG_0 || insn->off >1 || + (insn->off ==1 && opcode !=BPF_MOD && opcode !=BPF_DIV )) {verbose (env,"BPF_ALU uses reserved fields\n" );return -EINVAL ; }
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 6/17 bpf: Fix jit blinding with new sdiv/smov insns
In reply to Yonghong SongHandle new insns properly in bpf_jit_blind_insn() function.
--- include/linux/filter.h | 14 ++++++++++---- kernel/bpf/core.c | 4 ++-- 2 files changed, 12 insertions(+), 6 deletions(-)
include/linux/filter.h +10 -4
@@ -93,22 +93,28 @@ struct ctl_table_header;/* ALU ops on registers, bpf_add|sub|...: dst_reg += src_reg */ -#define BPF_ALU64_REG (OP ,DST ,SRC ) \ +#define BPF_ALU64_REG_OFF (OP ,DST ,SRC ,OFF ) \ ((struct bpf_insn) { \ .code = BPF_ALU64 | BPF_OP(OP) | BPF_X, \ .dst_reg = DST, \ .src_reg = SRC, \ - .off = 0, \ + .off = OFF, \ .imm = 0 }) -#define BPF_ALU32_REG (OP ,DST ,SRC ) \ +#define BPF_ALU64_REG (OP ,DST ,SRC ) \ + BPF_ALU64_REG_OFF(OP, DST, SRC, 0) + +#define BPF_ALU32_REG_OFF (OP ,DST ,SRC ,OFF ) \ ((struct bpf_insn) { \ .code = BPF_ALU | BPF_OP(OP) | BPF_X, \ .dst_reg = DST, \ .src_reg = SRC, \ - .off = 0, \ + .off = OFF, \ .imm = 0 }) +#define BPF_ALU32_REG (OP ,DST ,SRC ) \ + BPF_ALU32_REG_OFF(OP, DST, SRC, 0) +/* ALU ops on immediates, bpf_add|sub|...: dst_reg += imm32 */ #define BPF_ALU64_IMM (OP ,DST ,IMM ) \
kernel/bpf/core.c +2 -2
@@ -1272,7 +1272,7 @@ static int bpf_jit_blind_insn(const struct bpf_insn *from,case BPF_ALU |BPF_MOD |BPF_K : *to++ =BPF_ALU32_IMM (BPF_MOV ,BPF_REG_AX , imm_rnd ^ from->imm); *to++ =BPF_ALU32_IMM (BPF_XOR ,BPF_REG_AX , imm_rnd); - *to++ =BPF_ALU32_REG (from->code, from->dst_reg,BPF_REG_AX ); + *to++ =BPF_ALU32_REG_OFF (from->code, from->dst_reg,BPF_REG_AX , from->off);break ;case BPF_ALU64 |BPF_ADD |BPF_K :
@@ -1286,7 +1286,7 @@ static int bpf_jit_blind_insn(const struct bpf_insn *from,case BPF_ALU64 |BPF_MOD |BPF_K : *to++ =BPF_ALU64_IMM (BPF_MOV ,BPF_REG_AX , imm_rnd ^ from->imm); *to++ =BPF_ALU64_IMM (BPF_XOR ,BPF_REG_AX , imm_rnd); - *to++ =BPF_ALU64_REG (from->code, from->dst_reg,BPF_REG_AX ); + *to++ =BPF_ALU64_REG_OFF (from->code, from->dst_reg,BPF_REG_AX , from->off);break ;case BPF_JMP |BPF_JEQ |BPF_K :
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 7/17 bpf: Support new 32bit offset jmp instruction
In reply to Yonghong SongAdd interpreter/jit/verifier support for 32bit offset jmp instruction. If a conditional jmp instruction needs more than 16bit offset, it can be simulated with a conditional jmp + a 32bit jmp insn.
--- arch/x86/net/bpf_jit_comp.c | 28 ++++++++++++++++++---------- kernel/bpf/core.c | 19 ++++++++++++++++--- kernel/bpf/verifier.c | 32 ++++++++++++++++++++++---------- 3 files changed, 56 insertions(+), 23 deletions(-)
arch/x86/net/bpf_jit_comp.c +18 -10
@@ -1815,16 +1815,24 @@ st: if (is_imm8(insn->off))break ;case BPF_JMP |BPF_JA : -if (insn->off ==-1 ) -/* -1 jmp instructions will always jump -* backwards two bytes. Explicitly handling -* this case avoids wasting too many passes -* when there are long sequences of replaced -* dead code. -*/ - jmp_offset =-2 ; -else - jmp_offset = addrs[i + insn->off] - addrs[i]; +case BPF_JMP32 |BPF_JA : +if (BPF_CLASS (insn->code) ==BPF_JMP ) { +if (insn->off ==-1 ) +/* -1 jmp instructions will always jump +* backwards two bytes. Explicitly handling +* this case avoids wasting too many passes +* when there are long sequences of replaced +* dead code. +*/ + jmp_offset =-2 ; +else + jmp_offset = addrs[i + insn->off] - addrs[i]; + }else { +if (insn->imm ==-1 ) + jmp_offset =-2 ; +else + jmp_offset = addrs[i + insn->imm] - addrs[i]; + }if (!jmp_offset) {/*
kernel/bpf/core.c +16 -3
@@ -373,7 +373,12 @@ static int bpf_adj_delta_to_off(struct bpf_insn *insn, u32 pos, s32 end_old, {const s32 off_min =S16_MIN , off_max =S16_MAX ;s32 delta = end_new - end_old; -s32 off = insn->off; +s32 off; + +if (insn->code == (BPF_JMP32 |BPF_JA )) + off = insn->imm; +else + off = insn->off;if (curr < pos && curr + off +1 >= end_old) off += delta;
@@ -381,8 +386,12 @@ static int bpf_adj_delta_to_off(struct bpf_insn *insn, u32 pos, s32 end_old, off -= delta;if (off < off_min || off > off_max)return -ERANGE ; -if (!probe_pass) - insn->off = off; +if (!probe_pass) { +if (insn->code == (BPF_JMP32 |BPF_JA )) + insn->imm = off; +else + insn->off = off; + }return 0 ; }
@@ -1593,6 +1602,7 @@ EXPORT_SYMBOL_GPL(__bpf_call_base);INSN_3 (JMP ,JSLE ,K ), \INSN_3 (JMP ,JSET ,K ), \INSN_2 (JMP ,JA ), \ +INSN_2 (JMP32 ,JA ), \/* Store instructions. */ \/* Register based. */ \ INSN_3(STX, MEM, B), \
@@ -1989,6 +1999,9 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) JMP_JA: insn += insn->off;CONT ; + JMP32_JA: + insn += insn->imm; +CONT ; JMP_EXIT:return BPF_R0 ;/* JMP */
kernel/bpf/verifier.c +22 -10
@@ -2855,7 +2855,10 @@ static int check_subprogs(struct bpf_verifier_env *env) goto next;if (BPF_OP (code) ==BPF_EXIT ||BPF_OP (code) ==BPF_CALL ) goto next; - off = i + insn[i].off +1 ; +if (code == (BPF_JMP32 |BPF_JA )) + off = i + insn[i].imm +1 ; +else + off = i + insn[i].off +1 ;if (off < subprog_start || off >= subprog_end) {verbose (env,"jump out of range from insn %d to %d\n" , i, off);return -EINVAL ;
@@ -2867,6 +2870,7 @@ static int check_subprogs(struct bpf_verifier_env *env)* or unconditional jump back */ if (code != (BPF_JMP |BPF_EXIT ) && + code != (BPF_JMP32 |BPF_JA ) && code != (BPF_JMP |BPF_JA )) {verbose (env,"last insn is not an exit or jmp\n" );return -EINVAL ;
@@ -14792,7 +14796,7 @@ static int visit_func_call_insn(int t, struct bpf_insn *insns,static int visit_insn (int t,struct bpf_verifier_env *env) {struct bpf_insn *insns = env->prog->insnsi, *insn = &insns[t]; -int ret; +int ret, off;if (bpf_pseudo_func (insn))return visit_func_call_insn (t, insns, env, true);
@@ -14840,14 +14844,19 @@ static int visit_insn(int t, struct bpf_verifier_env *env)if (BPF_SRC (insn->code) !=BPF_K )return -EINVAL ; +if (BPF_CLASS (insn->code) ==BPF_JMP ) + off = insn->off; +else + off = insn->imm; +/* unconditional jump with single edge */ - ret =push_insn (t, t + insn->off +1 ,FALLTHROUGH , env, + ret =push_insn (t, t + off +1 ,FALLTHROUGH , env, true);if (ret)return ret; -mark_prune_point (env, t + insn->off +1 ); -mark_jmp_point (env, t + insn->off +1 ); +mark_prune_point (env, t + off +1 ); +mark_jmp_point (env, t + off +1 );return ret;
@@ -16643,15 +16652,18 @@ static int do_check(struct bpf_verifier_env *env)mark_reg_scratched (env,BPF_REG_0 ); }else if (opcode ==BPF_JA ) {if (BPF_SRC (insn->code) !=BPF_K || - insn->imm !=0 || insn->src_reg !=BPF_REG_0 || insn->dst_reg !=BPF_REG_0 || - class ==BPF_JMP32 ) { + (class ==BPF_JMP && insn->imm !=0 ) || + (class ==BPF_JMP32 && insn->off !=0 )) {verbose (env,"BPF_JA uses reserved fields\n" );return -EINVAL ; } - env->insn_idx += insn->off +1 ; +if (class ==BPF_JMP ) + env->insn_idx += insn->off +1 ; +else + env->insn_idx += insn->imm +1 ;continue ; }else if (opcode ==BPF_EXIT ) {
@@ -17498,13 +17510,13 @@ static bool insn_is_cond_jump(u8 code) {u8 op; + op =BPF_OP (code);if (BPF_CLASS (code) ==BPF_JMP32 ) -return true; +return op !=BPF_JA ;if (BPF_CLASS (code) !=BPF_JMP )return false; - op =BPF_OP (code);return op !=BPF_JA && op !=BPF_EXIT && op !=BPF_CALL ; }
Signature · 1 line
2.34.1
Re: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Hi Yonghong Song,
Greetings!
I used Syzkaller and found that there is WARNING in __mark_chain_precision in linux-next tag - next-20250414.
After bisection and the first bad commit is:
"4cd58e9af8b9 bpf: Support new 32bit offset jmp instruction "
All detailed into can be found at:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision
Syzkaller repro code:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.c
Syzkaller repro syscall steps:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.prog
Syzkaller report:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.report
Kconfig(make olddefconfig):
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/kconfig_origin
Bisect info:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/bisect_info.log
bzImage:
https://github.com/laifryiee/syzkaller_logs/raw/refs/heads/main/250415_203801___mark_chain_precision/bzImage_8ffd015db85fea3e15a77027fda6c02ced4d2444
Issue dmesg:
https://github.com/laifryiee/syzkaller_logs/blob/main/250415_203801___mark_chain_precision/8ffd015db85fea3e15a77027fda6c02ced4d2444_dmesg.log
"
[ 51.167546] ------------[ cut here ]------------ [ 51.167803] verifier backtracking bug [ 51.167867] WARNING: CPU: 1 PID: 672 at kernel/bpf/verifier.c:4302 __mark_chain_precision+0x35d3/0x37b0 [ 51.168496] Modules linked in: [ 51.168684] CPU: 1 UID: 0 PID: 672 Comm: repro Not tainted 6.15.0-rc2-8ffd015db85f #1 PREEMPT(voluntary) [ 51.169127] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.o4 [ 51.169980] RIP: 0010:__mark_chain_precision+0x35d3/0x37b0 [ 51.170255] Code: 06 31 ff 89 de e8 cd 0b e0 ff 84 db 0f 85 a7 e5 ff ff e8 90 11 e0 ff 48 c7 c7 a0 cb f4 85 c6 05 f [ 51.171108] RSP: 0018:ffff8880115ff2d8 EFLAGS: 00010296 [ 51.171424] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff81470f72 [ 51.171759] RDX: ffff88801f422540 RSI: ffffffff81470f7f RDI: 0000000000000001 [ 51.172112] RBP: ffff8880115ff428 R08: 0000000000000001 R09: ffffed100d8a5941 [ 51.172443] R10: 0000000000000000 R11: ffff88801f423398 R12: 0000000000000400 [ 51.172769] R13: dffffc0000000000 R14: 0000000000000002 R15: ffff88801f720000 [ 51.173152] FS: 00007f8a0a0b1600(0000) GS:ffff8880e3684000(0000) knlGS:0000000000000000 [ 51.173563] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 51.173861] CR2: 0000000000402010 CR3: 000000001179a006 CR4: 0000000000770ef0 [ 51.174244] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 51.174614] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400 [ 51.174995] PKRU: 55555554 [ 51.175151] Call Trace: [ 51.175302] <TASK> [ 51.175439] ? __lock_acquire+0x381/0x2260 [ 51.175675] ? __pfx___sanitizer_cov_trace_const_cmp4+0x10/0x10 [ 51.176006] ? __pfx___mark_chain_precision+0x10/0x10 [ 51.176326] ? mark_reg_read+0x1e4/0x340 [ 51.176558] ? __check_reg_arg+0x1c8/0x440 [ 51.176802] ? kasan_quarantine_put+0xa2/0x200 [ 51.177068] check_cond_jmp_op+0x2692/0x65f0 [ 51.177335] ? krealloc_noprof+0xe5/0x330 [ 51.177569] ? krealloc_noprof+0x190/0x330 [ 51.177790] ? __pfx_check_cond_jmp_op+0x10/0x10 [ 51.178060] ? push_insn_history+0x1d0/0x6d0 [ 51.178308] do_check_common+0x9134/0xd570 [ 51.178532] ? ns_capable+0xec/0x130 [ 51.178748] ? bpf_base_func_proto+0x7e/0xbe0 [ 51.179025] ? __sanitizer_cov_trace_const_cmp1+0x1e/0x30 [ 51.179319] ? __pfx_do_check_common+0x10/0x10 [ 51.179540] ? __pfx_mark_fastcall_pattern_for_call+0x10/0x10 [ 51.179864] ? bpf_check+0x89b9/0xd880 [ 51.180072] ? kvfree+0x32/0x40 [ 51.180237] bpf_check+0x9c27/0xd880 [ 51.180450] ? rcu_is_watching+0x19/0xc0 [ 51.180680] ? __lock_acquire+0x380/0x2260 [ 51.180900] ? __pfx_bpf_check+0x10/0x10 [ 51.181099] ? __lock_acquire+0x410/0x2260 [ 51.181355] ? __this_cpu_preempt_check+0x21/0x30 [ 51.181673] ? seqcount_lockdep_reader_access.constprop.0+0xb4/0xd0 [ 51.181989] ? __sanitizer_cov_trace_cmp4+0x1a/0x20 [ 51.182229] ? __sanitizer_cov_trace_const_cmp1+0x1e/0x30 [ 51.182510] ? bpf_obj_name_cpy+0x152/0x1b0 [ 51.182765] bpf_prog_load+0x14d7/0x2600 [ 51.182970] ? __pfx_bpf_prog_load+0x10/0x10 [ 51.183193] ? __might_fault+0x14a/0x1b0 [ 51.183435] ? __this_cpu_preempt_check+0x21/0x30 [ 51.183670] ? lock_release+0x14f/0x2c0 [ 51.183876] ? __might_fault+0xf1/0x1b0 [ 51.184074] __sys_bpf+0x18ac/0x5c10 [ 51.184279] ? __pfx___sys_bpf+0x10/0x10 [ 51.184502] ? __lock_acquire+0x410/0x2260 [ 51.184725] ? __sanitizer_cov_trace_cmp4+0x1a/0x20 [ 51.184960] ? ktime_get_coarse_real_ts64+0xb6/0x100 [ 51.185253] ? __audit_syscall_entry+0x39c/0x500 [ 51.185507] __x64_sys_bpf+0x7d/0xc0 [ 51.185718] ? syscall_trace_enter+0x14d/0x280 [ 51.185945] x64_sys_call+0x204a/0x2150 [ 51.186182] do_syscall_64+0x6d/0x150 [ 51.186395] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 51.186654] RIP: 0033:0x7f8a09e3ee5d [ 51.186869] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 8 [ 51.187767] RSP: 002b:00007fff00100bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 [ 51.188152] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8a09e3ee5d [ 51.188527] RDX: 0000000000000090 RSI: 00000000200009c0 RDI: 0000000000000005 [ 51.188895] RBP: 00007fff00100bc0 R08: 0000000000000000 R09: 0000000000000001 [ 51.189263] R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff00100cd8 [ 51.189657] R13: 0000000000401146 R14: 0000000000403e08 R15: 00007f8a0a0fa000 [ 51.190071] </TASK> [ 51.190197] irq event stamp: 3113 [ 51.190380] hardirqs last enabled at (3121): [<ffffffff8165d8c5>] __up_console_sem+0x95/0xb0 [ 51.190797] hardirqs last disabled at (3128): [<ffffffff8165d8aa>] __up_console_sem+0x7a/0xb0 [ 51.191214] softirqs last enabled at (2600): [<ffffffff8149050e>] __irq_exit_rcu+0x10e/0x170 [ 51.191656] softirqs last disabled at (2589): [<ffffffff8149050e>] __irq_exit_rcu+0x10e/0x170 [ 51.192093] ---[ end trace 0000000000000000 ]---
"
Hope this cound be insightful to you.
Regards,
Yi Lai
---
If you don't need the following environment to reproduce the problem or if you already have one reproduced environment, please ignore the following information.
How to reproduce:
git clone https://gitlab.com/xupengfe/repro_vm_env.git
cd repro_vm_env
tar -xvf repro_vm_env.tar.gz
cd repro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
// start3.sh will load bzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65 v6.2-rc5 kernel
// You could change the bzImage_xxx as you want
// Maybe you need to remove line "-drive if=pflash,format=raw,readonly=on,file=./OVMF_CODE.fd \" for different qemu version
You could use below command to log in, there is no password for root.
ssh -p 10023 root@localhost
After login vm(virtual machine) successfully, you could transfer reproduced binary to the vm by below way, and reproduce the problem in vm:
gcc -pthread -o repro repro.c
scp -P 10023 repro root@localhost:/root/
Get the bzImage for target kernel:
Please use target kconfig and copy it to kernel_src/.config make olddefconfig
make -jx bzImage //x should equal or less than cpu num your pc has
Fill the bzImage file into above start3.sh to load the target kernel in vm.
Tips:
If you already have qemu-system-x86_64, please ignore below info.
If you want to install qemu v7.1.0 version:
git clone https://github.com/qemu/qemu.git
cd qemu
git checkout -f v7.1.0
mkdir build
cd build
yum install -y ninja-build.x86_64
yum -y install libslirp-devel.x86_64
../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl --enable-usb-redir --enable-slirp make
make install
Quoted 199 lines · Yonghong Song
Add interpreter/jit/verifier support for 32bit offset jmp instruction. If a conditional jmp instruction needs more than 16bit offset, it can be simulated with a conditional jmp + a 32bit jmp insn.
Acked-by Eduard Zingerman <[email protected]>Signed-off-by Yonghong Song <[email protected]>--- arch/x86/net/bpf_jit_comp.c | 28 ++++++++++++++++++---------- kernel/bpf/core.c | 19 ++++++++++++++++--- kernel/bpf/verifier.c | 32 ++++++++++++++++++++++---------- 3 files changed, 56 insertions(+), 23 deletions(-)arch/x86/net/bpf_jit_comp.c +18
-10@@ -1815,16 +1815,24 @@ st: if (is_imm8(insn->off))break ;case BPF_JMP |BPF_JA : -if (insn->off ==-1 ) -/* -1 jmp instructions will always jump -* backwards two bytes. Explicitly handling -* this case avoids wasting too many passes -* when there are long sequences of replaced -* dead code. -*/ - jmp_offset =-2 ; -else - jmp_offset = addrs[i + insn->off] - addrs[i]; +case BPF_JMP32 |BPF_JA : +if (BPF_CLASS (insn->code) ==BPF_JMP ) { +if (insn->off ==-1 ) +/* -1 jmp instructions will always jump +* backwards two bytes. Explicitly handling +* this case avoids wasting too many passes +* when there are long sequences of replaced +* dead code. +*/ + jmp_offset =-2 ; +else + jmp_offset = addrs[i + insn->off] - addrs[i]; + }else { +if (insn->imm ==-1 ) + jmp_offset =-2 ; +else + jmp_offset = addrs[i + insn->imm] - addrs[i]; + }if (!jmp_offset) {/* kernel/bpf/core.c +16
-3@@ -373,7 +373,12 @@ static int bpf_adj_delta_to_off(struct bpf_insn *insn, u32 pos, s32 end_old, {const s32 off_min =S16_MIN , off_max =S16_MAX ;s32 delta = end_new - end_old; -s32 off = insn->off; +s32 off; + +if (insn->code == (BPF_JMP32 |BPF_JA )) + off = insn->imm; +else + off = insn->off;if (curr < pos && curr + off +1 >= end_old) off += delta;@@ -381,8 +386,12 @@ static int bpf_adj_delta_to_off(struct bpf_insn *insn, u32 pos, s32 end_old, off -= delta;if (off < off_min || off > off_max)return -ERANGE ; -if (!probe_pass) - insn->off = off; +if (!probe_pass) { +if (insn->code == (BPF_JMP32 |BPF_JA )) + insn->imm = off; +else + insn->off = off; + }return 0 ; }@@ -1593,6 +1602,7 @@ EXPORT_SYMBOL_GPL(__bpf_call_base);INSN_3 (JMP ,JSLE ,K ), \INSN_3 (JMP ,JSET ,K ), \INSN_2 (JMP ,JA ), \ +INSN_2 (JMP32 ,JA ), \/* Store instructions. */ \/* Register based. */ \ INSN_3(STX, MEM, B), \@@ -1989,6 +1999,9 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) JMP_JA: insn += insn->off;CONT ; + JMP32_JA: + insn += insn->imm; +CONT ; JMP_EXIT:return BPF_R0 ;/* JMP */ kernel/bpf/verifier.c +22
-10@@ -2855,7 +2855,10 @@ static int check_subprogs(struct bpf_verifier_env *env) goto next;if (BPF_OP (code) ==BPF_EXIT ||BPF_OP (code) ==BPF_CALL ) goto next; - off = i + insn[i].off +1 ; +if (code == (BPF_JMP32 |BPF_JA )) + off = i + insn[i].imm +1 ; +else + off = i + insn[i].off +1 ;if (off < subprog_start || off >= subprog_end) {verbose (env,"jump out of range from insn %d to %d\n" , i, off);return -EINVAL ;@@ -2867,6 +2870,7 @@ static int check_subprogs(struct bpf_verifier_env *env)* or unconditional jump back */ if (code != (BPF_JMP |BPF_EXIT ) && + code != (BPF_JMP32 |BPF_JA ) && code != (BPF_JMP |BPF_JA )) {verbose (env,"last insn is not an exit or jmp\n" );return -EINVAL ;@@ -14792,7 +14796,7 @@ static int visit_func_call_insn(int t, struct bpf_insn *insns,static int visit_insn (int t,struct bpf_verifier_env *env) {struct bpf_insn *insns = env->prog->insnsi, *insn = &insns[t]; -int ret; +int ret, off;if (bpf_pseudo_func (insn))return visit_func_call_insn (t, insns, env, true);@@ -14840,14 +14844,19 @@ static int visit_insn(int t, struct bpf_verifier_env *env)if (BPF_SRC (insn->code) !=BPF_K )return -EINVAL ; +if (BPF_CLASS (insn->code) ==BPF_JMP ) + off = insn->off; +else + off = insn->imm; +/* unconditional jump with single edge */ - ret =push_insn (t, t + insn->off +1 ,FALLTHROUGH , env, + ret =push_insn (t, t + off +1 ,FALLTHROUGH , env, true);if (ret)return ret; -mark_prune_point (env, t + insn->off +1 ); -mark_jmp_point (env, t + insn->off +1 ); +mark_prune_point (env, t + off +1 ); +mark_jmp_point (env, t + off +1 );return ret;@@ -16643,15 +16652,18 @@ static int do_check(struct bpf_verifier_env *env)mark_reg_scratched (env,BPF_REG_0 ); }else if (opcode ==BPF_JA ) {if (BPF_SRC (insn->code) !=BPF_K || - insn->imm !=0 || insn->src_reg !=BPF_REG_0 || insn->dst_reg !=BPF_REG_0 || - class ==BPF_JMP32 ) { + (class ==BPF_JMP && insn->imm !=0 ) || + (class ==BPF_JMP32 && insn->off !=0 )) {verbose (env,"BPF_JA uses reserved fields\n" );return -EINVAL ; } - env->insn_idx += insn->off +1 ; +if (class ==BPF_JMP ) + env->insn_idx += insn->off +1 ; +else + env->insn_idx += insn->imm +1 ;continue ; }else if (opcode ==BPF_EXIT ) {@@ -17498,13 +17510,13 @@ static bool insn_is_cond_jump(u8 code) {u8 op; + op =BPF_OP (code);if (BPF_CLASS (code) ==BPF_JMP32 ) -return true; +return op !=BPF_JA ;if (BPF_CLASS (code) !=BPF_JMP )return false; - op =BPF_OP (code);return op !=BPF_JA && op !=BPF_EXIT && op !=BPF_CALL ; }Signature · 1 line
2.34.1
Yonghong Song
reviewerRe: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Quoted 5 lines · Yi
Hi Yonghong Song,
Greetings!
I used Syzkaller and found that there is WARNING in
__mark_chain_precisionin linux-next tag - next-20250414.
Thanks, Yi. I will investigate this soon.
Quoted 157 lines
After bisection and the first bad commit is:
"4cd58e9af8b9bpf: Support new 32bit offset jmp instruction "All detailed into can be found at:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision
Syzkaller repro code:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.c
Syzkaller repro syscall steps:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.prog
Syzkaller report:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.report
Kconfig(make olddefconfig):
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/kconfig_origin
Bisect info:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/bisect_info.log
bzImage:
https://github.com/laifryiee/syzkaller_logs/raw/refs/heads/main/250415_203801___mark_chain_precision/bzImage_8ffd015db85fea3e15a77027fda6c02ced4d2444
Issue dmesg:
https://github.com/laifryiee/syzkaller_logs/blob/main/250415_203801___mark_chain_precision/8ffd015db85fea3e15a77027fda6c02ced4d2444_dmesg.log"
[ 51.167546] ------------[ cut here ]------------ [ 51.167803] verifier backtracking bug [ 51.167867] WARNING: CPU: 1 PID: 672 at kernel/bpf/verifier.c:4302 __mark_chain_precision+0x35d3/0x37b0 [ 51.168496] Modules linked in: [ 51.168684] CPU: 1 UID: 0 PID: 672 Comm: repro Not tainted 6.15.0-rc2-8ffd015db85f #1 PREEMPT(voluntary) [ 51.169127] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.o4 [ 51.169980] RIP: 0010:__mark_chain_precision+0x35d3/0x37b0 [ 51.170255] Code: 06 31 ff 89 de e8 cd 0b e0 ff 84 db 0f 85 a7 e5 ff ff e8 90 11 e0 ff 48 c7 c7 a0 cb f4 85 c6 05 f [ 51.171108] RSP: 0018:ffff8880115ff2d8 EFLAGS: 00010296 [ 51.171424] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff81470f72 [ 51.171759] RDX: ffff88801f422540 RSI: ffffffff81470f7f RDI: 0000000000000001 [ 51.172112] RBP: ffff8880115ff428 R08: 0000000000000001 R09: ffffed100d8a5941 [ 51.172443] R10: 0000000000000000 R11: ffff88801f423398 R12: 0000000000000400 [ 51.172769] R13: dffffc0000000000 R14: 0000000000000002 R15: ffff88801f720000 [ 51.173152] FS: 00007f8a0a0b1600(0000) GS:ffff8880e3684000(0000) knlGS:0000000000000000 [ 51.173563] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 51.173861] CR2: 0000000000402010 CR3: 000000001179a006 CR4: 0000000000770ef0 [ 51.174244] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 51.174614] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400 [ 51.174995] PKRU: 55555554 [ 51.175151] Call Trace: [ 51.175302] <TASK> [ 51.175439] ? __lock_acquire+0x381/0x2260 [ 51.175675] ? __pfx___sanitizer_cov_trace_const_cmp4+0x10/0x10 [ 51.176006] ? __pfx___mark_chain_precision+0x10/0x10 [ 51.176326] ? mark_reg_read+0x1e4/0x340 [ 51.176558] ? __check_reg_arg+0x1c8/0x440 [ 51.176802] ? kasan_quarantine_put+0xa2/0x200 [ 51.177068] check_cond_jmp_op+0x2692/0x65f0 [ 51.177335] ? krealloc_noprof+0xe5/0x330 [ 51.177569] ? krealloc_noprof+0x190/0x330 [ 51.177790] ? __pfx_check_cond_jmp_op+0x10/0x10 [ 51.178060] ? push_insn_history+0x1d0/0x6d0 [ 51.178308] do_check_common+0x9134/0xd570 [ 51.178532] ? ns_capable+0xec/0x130 [ 51.178748] ? bpf_base_func_proto+0x7e/0xbe0 [ 51.179025] ? __sanitizer_cov_trace_const_cmp1+0x1e/0x30 [ 51.179319] ? __pfx_do_check_common+0x10/0x10 [ 51.179540] ? __pfx_mark_fastcall_pattern_for_call+0x10/0x10 [ 51.179864] ? bpf_check+0x89b9/0xd880 [ 51.180072] ? kvfree+0x32/0x40 [ 51.180237] bpf_check+0x9c27/0xd880 [ 51.180450] ? rcu_is_watching+0x19/0xc0 [ 51.180680] ? __lock_acquire+0x380/0x2260 [ 51.180900] ? __pfx_bpf_check+0x10/0x10 [ 51.181099] ? __lock_acquire+0x410/0x2260 [ 51.181355] ? __this_cpu_preempt_check+0x21/0x30 [ 51.181673] ? seqcount_lockdep_reader_access.constprop.0+0xb4/0xd0 [ 51.181989] ? __sanitizer_cov_trace_cmp4+0x1a/0x20 [ 51.182229] ? __sanitizer_cov_trace_const_cmp1+0x1e/0x30 [ 51.182510] ? bpf_obj_name_cpy+0x152/0x1b0 [ 51.182765] bpf_prog_load+0x14d7/0x2600 [ 51.182970] ? __pfx_bpf_prog_load+0x10/0x10 [ 51.183193] ? __might_fault+0x14a/0x1b0 [ 51.183435] ? __this_cpu_preempt_check+0x21/0x30 [ 51.183670] ? lock_release+0x14f/0x2c0 [ 51.183876] ? __might_fault+0xf1/0x1b0 [ 51.184074] __sys_bpf+0x18ac/0x5c10 [ 51.184279] ? __pfx___sys_bpf+0x10/0x10 [ 51.184502] ? __lock_acquire+0x410/0x2260 [ 51.184725] ? __sanitizer_cov_trace_cmp4+0x1a/0x20 [ 51.184960] ? ktime_get_coarse_real_ts64+0xb6/0x100 [ 51.185253] ? __audit_syscall_entry+0x39c/0x500 [ 51.185507] __x64_sys_bpf+0x7d/0xc0 [ 51.185718] ? syscall_trace_enter+0x14d/0x280 [ 51.185945] x64_sys_call+0x204a/0x2150 [ 51.186182] do_syscall_64+0x6d/0x150 [ 51.186395] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 51.186654] RIP: 0033:0x7f8a09e3ee5d [ 51.186869] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 8 [ 51.187767] RSP: 002b:00007fff00100bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 [ 51.188152] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8a09e3ee5d [ 51.188527] RDX: 0000000000000090 RSI: 00000000200009c0 RDI: 0000000000000005 [ 51.188895] RBP: 00007fff00100bc0 R08: 0000000000000000 R09: 0000000000000001 [ 51.189263] R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff00100cd8 [ 51.189657] R13: 0000000000401146 R14: 0000000000403e08 R15: 00007f8a0a0fa000 [ 51.190071] </TASK> [ 51.190197] irq event stamp: 3113 [ 51.190380] hardirqs last enabled at (3121): [<ffffffff8165d8c5>] __up_console_sem+0x95/0xb0 [ 51.190797] hardirqs last disabled at (3128): [<ffffffff8165d8aa>] __up_console_sem+0x7a/0xb0 [ 51.191214] softirqs last enabled at (2600): [<ffffffff8149050e>] __irq_exit_rcu+0x10e/0x170 [ 51.191656] softirqs last disabled at (2589): [<ffffffff8149050e>] __irq_exit_rcu+0x10e/0x170 [ 51.192093] ---[ end trace 0000000000000000 ]---"
Hope this cound be insightful to you.
Regards,
Yi Lai---
If you don't need the following environment to reproduce the problem or if you already have one reproduced environment, please ignore the following information.
How to reproduce:
git clone https://gitlab.com/xupengfe/repro_vm_env.git
cdrepro_vm_env
tar -xvf repro_vm_env.tar.gz
cdrepro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
//start3.shwill loadbzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65v6.2-rc5 kernel
// You could change thebzImage_xxxas you want
// Maybe you need to remove line "-drive if=pflash,format=raw,readonly=on,file=./OVMF_CODE.fd \" for different qemu version
You could use below command to log in, there is no password for root.
ssh -p 10023 root@localhostAfter login vm(virtual machine) successfully, you could transfer reproduced binary to the vm by below way, and reproduce the problem in vm:
gcc -pthread -o reprorepro.c
scp -P 10023 repro root@localhost:/root/Get the bzImage for target kernel:
Please use target kconfig and copy it to kernel_src/.config make olddefconfig
make -jx bzImage //x should equal or less than cpu num your pc hasFill the bzImage file into above
start3.shto load the target kernel in vm.Tips:
If you already have qemu-system-x86_64, please ignore below info.
If you want to install qemu v7.1.0 version:
git clone https://github.com/qemu/qemu.git
cd qemu
git checkout -f v7.1.0
mkdir build
cd build
yum install -y ninja-build.x86_64
yum -y install libslirp-devel.x86_64
../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl --enable-usb-redir --enable-slirp make
make install
[...]
Yonghong Song
reviewerRe: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Quoted 10 lines · Yonghong Song
Quoted 5 lines · Yi
Hi Yonghong Song,
Greetings!
I used Syzkaller and found that there is WARNING in
__mark_chain_precisionin linux-next tag - next-20250414.Thanks, Yi. I will investigate this soon.
I did some investigation. The source code looks like below:
+__used __naked static void hack_sub(void)
+{
+ asm volatile (" \
+ r2 = 2314885393468386424 ll; \ + gotol +0; \ + if r2 <= r10 goto -1; \ + if r1 >= -1835016 goto +0; \ + if r2 <= 8 goto +0; \ + if r3 <= 0 goto +0; \ + call 44; \ + exit; \ + " : + : + : __clobber_all);
+}
+
+SEC("cgroup/sock_create")
+__description("HACK")
+__success __retval(0)
+__naked void hack(void)
+{
+ asm volatile (" \
+ r3 = 0 ll; \ + call hack_sub; \ + exit; \ + " : + : + : __clobber_all);
+}
The verification failure:
0: R1=ctx() R10=fp0
; asm volatile (" \ @ verifier_movsx.c:352
0: (18) r3 = 0x0 ; R3_w=0
2: (85) call pc+1
caller:
R10=fp0
callee:
frame1: R1=ctx() R3_w=0 R10=fp0
4: frame1: R1=ctx() R3_w=0 R10=fp0
; asm volatile (" \ @ verifier_movsx.c:333
4: (18) r2 = 0x20202000256c6c78 ; frame1: R2_w=0x20202000256c6c78
6: (06) gotol pc+0
7: (bd) if r2 <= r10 goto pc-1 ; frame1: R2_w=0x20202000256c6c78 R10=fp0
8: (35) if r1 >= 0xffe3fff8 goto pc+0 ; frame1: R1=ctx()
9: (b5) if r2 <= 0x8 goto pc+0mark_precise: frame1: last_idx 9 first_idx 0 subseq_idx -1mark_precise: frame1: regs=r2 stack= before 8: (35) if r1 >= 0xffe3fff8 goto pc+0mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0mark_precise: frame1: regs=r2,r10 stack= before 4: (18) r2 = 0x20202000256c6c78mark_precise: frame1: regs=r10 stack= before 2: (85) call pc+1
BUG regs 400
processed 7 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
The verification failure happens below (line 4301 and 4302)
4294 /* static subprog call instruction, which
4295 * means that we are exiting current subprog,
4296 * so only r1-r5 could be still requested as
4297 * precise, r0 and r6-r10 or any stack slot in
4298 * the current frame should be zero by now
4299 */
4300 if (bt_reg_mask(bt) & ~BPF_REGMASK_ARGS) {
4301 verbose(env, "BUG regs %x\n", bt_reg_mask(bt));
4302 WARN_ONCE(1, "verifier backtracking bug");
4303 return -EFAULT;4304 }
So the failure reason is due to r10 is used during comparisons. So verifier does the right thing. Maybe you should remove WARN_ONCE ("verifier backtracking bug")? Do we actually hit backtracking bug due to verifier implementation?
Quoted 169 lines
Quoted 167 lines
After bisection and the first bad commit is:
"4cd58e9af8b9bpf: Support new 32bit offset jmp instruction "All detailed into can be found at:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precisionSyzkaller repro code:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.cSyzkaller repro syscall steps:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.progSyzkaller report:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/repro.reportKconfig(make olddefconfig):
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/kconfig_originBisect info:
https://github.com/laifryiee/syzkaller_logs/tree/main/250415_203801___mark_chain_precision/bisect_info.log"
[ 51.167546] ------------[ cut here ]------------
[ 51.167803] verifier backtracking bug
[ 51.167867] WARNING: CPU: 1 PID: 672 atkernel/bpf/verifier.c:4302__mark_chain_precision+0x35d3/0x37b0[ 51.168496] Modules linked in:
[ 51.168684] CPU: 1 UID: 0 PID: 672 Comm: repro Not tainted 6.15.0-rc2-8ffd015db85f #1 PREEMPT(voluntary) [ 51.169127] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.o4 [ 51.169980] RIP: 0010:__mark_chain_precision+0x35d3/0x37b0
[ 51.170255] Code: 06 31 ff 89 de e8 cd 0b e0 ff 84 db 0f 85 a7 e5 ff ff e8 90 11 e0 ff 48 c7 c7 a0 cb f4 85 c6 05 f [ 51.171108] RSP: 0018:ffff8880115ff2d8 EFLAGS: 00010296
[ 51.171424] RAX: 0000000000000000 RBX: 0000000000000000 RCX:ffffffff81470f72
[ 51.171759] RDX:ffff88801f422540RSI:ffffffff81470f7fRDI: 0000000000000001
[ 51.172112] RBP:ffff8880115ff428R08: 0000000000000001 R09:ffffed100d8a5941
[ 51.172443] R10: 0000000000000000 R11:ffff88801f423398R12: 0000000000000400
[ 51.172769] R13:dffffc0000000000R14: 0000000000000002 R15:ffff88801f720000
[ 51.173152] FS: 00007f8a0a0b1600(0000) GS:ffff8880e3684000(0000) knlGS:0000000000000000
[ 51.173563] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 51.173861] CR2: 0000000000402010 CR3:000000001179a006CR4:0000000000770ef0
[ 51.174244] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 51.174614] DR3: 0000000000000000 DR6:00000000ffff07f0DR7: 0000000000000400
[ 51.174995] PKRU: 55555554
[ 51.175151] Call Trace:
[ 51.175302] <TASK>
[ 51.175439] ?__lock_acquire+0x381/0x2260
[ 51.175675] ?__pfx___sanitizer_cov_trace_const_cmp4+0x10/0x10
[ 51.176006] ?__pfx___mark_chain_precision+0x10/0x10
[ 51.176326] ?mark_reg_read+0x1e4/0x340
[ 51.176558] ?__check_reg_arg+0x1c8/0x440
[ 51.176802] ?kasan_quarantine_put+0xa2/0x200
[ 51.177068]check_cond_jmp_op+0x2692/0x65f0
[ 51.177335] ?krealloc_noprof+0xe5/0x330
[ 51.177569] ?krealloc_noprof+0x190/0x330
[ 51.177790] ?__pfx_check_cond_jmp_op+0x10/0x10
[ 51.178060] ?push_insn_history+0x1d0/0x6d0
[ 51.178308]do_check_common+0x9134/0xd570
[ 51.178532] ?ns_capable+0xec/0x130
[ 51.178748] ?bpf_base_func_proto+0x7e/0xbe0
[ 51.179025] ?__sanitizer_cov_trace_const_cmp1+0x1e/0x30
[ 51.179319] ?__pfx_do_check_common+0x10/0x10
[ 51.179540] ?__pfx_mark_fastcall_pattern_for_call+0x10/0x10
[ 51.179864] ?bpf_check+0x89b9/0xd880
[ 51.180072] ?kvfree+0x32/0x40
[ 51.180237]bpf_check+0x9c27/0xd880
[ 51.180450] ?rcu_is_watching+0x19/0xc0
[ 51.180680] ?__lock_acquire+0x380/0x2260
[ 51.180900] ?__pfx_bpf_check+0x10/0x10
[ 51.181099] ?__lock_acquire+0x410/0x2260
[ 51.181355] ?__this_cpu_preempt_check+0x21/0x30
[ 51.181673] ? seqcount_lockdep_reader_access.constprop.0+0xb4/0xd0
[ 51.181989] ?__sanitizer_cov_trace_cmp4+0x1a/0x20
[ 51.182229] ?__sanitizer_cov_trace_const_cmp1+0x1e/0x30
[ 51.182510] ?bpf_obj_name_cpy+0x152/0x1b0
[ 51.182765]bpf_prog_load+0x14d7/0x2600
[ 51.182970] ?__pfx_bpf_prog_load+0x10/0x10
[ 51.183193] ?__might_fault+0x14a/0x1b0
[ 51.183435] ?__this_cpu_preempt_check+0x21/0x30
[ 51.183670] ?lock_release+0x14f/0x2c0
[ 51.183876] ?__might_fault+0xf1/0x1b0
[ 51.184074]__sys_bpf+0x18ac/0x5c10
[ 51.184279] ?__pfx___sys_bpf+0x10/0x10
[ 51.184502] ?__lock_acquire+0x410/0x2260
[ 51.184725] ?__sanitizer_cov_trace_cmp4+0x1a/0x20
[ 51.184960] ?ktime_get_coarse_real_ts64+0xb6/0x100
[ 51.185253] ?__audit_syscall_entry+0x39c/0x500
[ 51.185507]__x64_sys_bpf+0x7d/0xc0
[ 51.185718] ?syscall_trace_enter+0x14d/0x280
[ 51.185945]x64_sys_call+0x204a/0x2150
[ 51.186182]do_syscall_64+0x6d/0x150
[ 51.186395]entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 51.186654] RIP: 0033:0x7f8a09e3ee5d
[ 51.186869] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 8 [ 51.187767] RSP: 002b:00007fff00100bb8 EFLAGS: 00000246ORIG_RAX: 0000000000000141
[ 51.188152] RAX: ffffffffffffffda RBX: 0000000000000000 RCX:00007f8a09e3ee5d
[ 51.188527] RDX: 0000000000000090 RSI:00000000200009c0RDI: 0000000000000005
[ 51.188895] RBP:00007fff00100bc0R08: 0000000000000000 R09: 0000000000000001
[ 51.189263] R10:00000000ffffffffR11: 0000000000000246 R12:00007fff00100cd8
[ 51.189657] R13: 0000000000401146 R14:0000000000403e08R15:00007f8a0a0fa000
[ 51.190071] </TASK>
[ 51.190197] irq event stamp: 3113
[ 51.190380] hardirqs last enabled at (3121): [<ffffffff8165d8c5>]__up_console_sem+0x95/0xb0
[ 51.190797] hardirqs last disabled at (3128): [<ffffffff8165d8aa>]__up_console_sem+0x7a/0xb0
[ 51.191214] softirqs last enabled at (2600): [<ffffffff8149050e>]__irq_exit_rcu+0x10e/0x170
[ 51.191656] softirqs last disabled at (2589): [<ffffffff8149050e>]__irq_exit_rcu+0x10e/0x170
[ 51.192093] ---[ end trace 0000000000000000 ]---
"Hope this cound be insightful to you.
Regards,
Yi Lai---
If you don't need the following environment to reproduce the problem or if you already have one reproduced environment, please ignore the following information.
How to reproduce:
git clone https://gitlab.com/xupengfe/repro_vm_env.git
cdrepro_vm_env
tar -xvf repro_vm_env.tar.gz
cdrepro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
//start3.shwill loadbzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65v6.2-rc5 kernel
// You could change thebzImage_xxxas you want
// Maybe you need to remove line "-drive if=pflash,format=raw,readonly=on,file=./OVMF_CODE.fd \" for different qemu version You could use below command to log in, there is no password for root.
ssh -p 10023 root@localhostAfter login vm(virtual machine) successfully, you could transfer reproduced binary to the vm by below way, and reproduce the problem in vm:
gcc -pthread -o reprorepro.c
scp -P 10023 repro root@localhost:/root/Get the bzImage for target kernel:
Please use target kconfig and copy it to kernel_src/.config
make olddefconfig
make -jx bzImage //x should equal or less than cpu num your pc hasFill the bzImage file into above
start3.shto load the target kernel in vm.Tips:
If you already have qemu-system-x86_64, please ignore below info. If you want to install qemu v7.1.0 version:
git clone https://github.com/qemu/qemu.git
cd qemu
git checkout -f v7.1.0
mkdir build
cd build
yum install -y ninja-build.x86_64
yum -y install libslirp-devel.x86_64
../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl --enable-usb-redir --enable-slirp make
make install[...]
Re: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Quoted 86 lines · Yonghong Song
Quoted 11 lines · Yonghong Song
Quoted 6 lines · Yi
Hi Yonghong Song,
Greetings!
I used Syzkaller and found that there is WARNING in
__mark_chain_precisionin linux-next tag - next-20250414.Thanks, Yi. I will investigate this soon.
I did some investigation. The source code looks like below:
(quoted diff) +29
-0+__used __naked static void hack_sub(void) +{ + asm volatile (" \ + r2 = 2314885393468386424 ll; \ + gotol +0; \ + if r2 <= r10 goto -1; \ + if r1 >= -1835016 goto +0; \ + if r2 <= 8 goto +0; \ + if r3 <= 0 goto +0; \ + call 44; \ + exit; \ + " : + : + : __clobber_all); +} + +SEC("cgroup/sock_create") +__description("HACK") +__success __retval(0) +__naked void hack(void) +{ + asm volatile (" \ + r3 = 0 ll; \ + call hack_sub; \ + exit; \ + " : + : + : __clobber_all); +}The verification failure:
0: R1=ctx() R10=fp0
; asm volatile (" \ @ verifier_movsx.c:352
0: (18) r3 =0x0; R3_w=0
2: (85) call pc+1
caller:
R10=fp0
callee:
frame1: R1=ctx() R3_w=0 R10=fp0
4: frame1: R1=ctx() R3_w=0 R10=fp0
; asm volatile (" \ @ verifier_movsx.c:333
4: (18) r2 =0x20202000256c6c78; frame1: R2_w=0x20202000256c6c78
6: (06) gotol pc+0
7: (bd) if r2 <= r10 goto pc-1 ; frame1: R2_w=0x20202000256c6c78 R10=fp0
8: (35) if r1 >=0xffe3fff8goto pc+0 ; frame1: R1=ctx()
9: (b5) if r2 <=0x8goto pc+0mark_precise: frame1:last_idx9first_idx0subseq_idx-1mark_precise: frame1: regs=r2 stack= before 8: (35) if r1 >=0xffe3fff8goto pc+0mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0mark_precise: frame1: regs=r2,r10 stack= before 4: (18) r2 =0x20202000256c6c78mark_precise: frame1: regs=r10 stack= before 2: (85) call pc+1
BUG regs 400
processed 7 insns (limit 1000000)max_states_per_insn0total_states0peak_states0mark_read0The verification failure happens below (line 4301 and 4302)
4294 /* static subprog call instruction, which
4295 * means that we are exiting current subprog, 4296 * so only r1-r5 could be still requested as 4297 * precise, r0 and r6-r10 or any stack slot in 4298 * the current frame should be zero by now 4299 */ 4300 if (bt_reg_mask(bt) & ~BPF_REGMASK_ARGS) { 4301 verbose(env, "BUG regs %x\n", bt_reg_mask(bt)); 4302 WARN_ONCE(1, "verifier backtracking bug"); 4303 return -EFAULT;
Quoted 6 lines
4304 }
So the failure reason is due to r10 is used during comparisons. So verifier does the right thing. Maybe you should remove
WARN_ONCE("verifier backtracking bug")? Do we actually hit backtracking bug due to verifier implementation?
hmm.
We probably should filter out r10 somehow,
since the following:
Quoted 2 lines
mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0
is already odd.
Andrii,
ideas?
Eduard Zingerman
maintainerRe: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
On Fri, 2025-05-09 at 10:21 -0700, Alexei Starovoitov wrote:
[...]
Quoted 7 lines
hmm.
We probably should filter out r10 somehow,
since the following:Quoted 2 lines
mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0is already odd.
Not Andrii, but here are my 5 cents.
check_cond_jmp() allows comparing pointers with scalars. is_branch_taken() predicts jumps for null comparisons.
Hence, tracking precision of the r2 above is correct. backtrack_insn() does not know the types of the registers when processing r2 <= r10 and thus adds r10 to the tracked set. Whenever a scalar is added to a PTR_TO_STACK such scalar is marked as precise. This means that there is no need to track precision for constituents of the PTR_TO_STACK values.
Given above, I think that filtering out r10 should be safe. In case if sequence of instructions would be more complex, e.g.:
r9 = r10 if r2 <= r9 goto -1; \
backtrack_insn() would still eventually get to r10 and stop propagation.
Re: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Quoted 24 lines · Eduard Zingerman
On Fri, 2025-05-09 at 10:21 -0700, Alexei Starovoitov wrote:
[...]
Quoted 7 lines
hmm.
We probably should filter out r10 somehow,
since the following:Quoted 2 lines
mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0is already odd.
Not Andrii, but here are my 5 cents.
check_cond_jmp()allows comparing pointers with scalars.is_branch_taken()predicts jumps for null comparisons.
Hence, tracking precision of the r2 above is correct.backtrack_insn()does not know the types of the registers when processingr2 <= r10and thus adds r10 to the tracked set. Whenever a scalar is added to aPTR_TO_STACKsuch scalar is marked as precise. This means that there is no need to track precision for constituents of thePTR_TO_STACKvalues.
Quoted 1 line
Given above, I think that filtering out r10 should be safe.
Yeah, it makes no sense to track r10. It's always "precise", effectively.
Quoted 8 lines
In case if sequence of instructions would be more complex, e.g.:
r9 = r10 if r2 <= r9 goto -1; \
backtrack_insn()would still eventually get to r10 and stop propagation.
Yonghong Song
reviewerRe: [PATCH bpf-next v5 07/17] bpf: Support new 32bit offset jmp instruction
Quoted 22 lines · Andrii Nakryiko
Quoted 21 lines · Eduard Zingerman
On Fri, 2025-05-09 at 10:21 -0700, Alexei Starovoitov wrote:
[...]
Quoted 6 lines
hmm.
We probably should filter out r10 somehow,
since the following:Quoted 2 lines
mark_precise: frame1: regs=r2 stack= before 7: (bd) if r2 <= r10 goto pc-1mark_precise: frame1: regs=r2,r10 stack= before 6: (06) gotol pc+0is already odd.
Not Andrii, but here are my 5 cents.
check_cond_jmp()allows comparing pointers with scalars.is_branch_taken()predicts jumps for null comparisons.
Hence, tracking precision of the r2 above is correct.backtrack_insn()does not know the types of the registers when processingr2 <= r10and thus adds r10 to the tracked set. Whenever a scalar is added to aPTR_TO_STACKsuch scalar is marked as precise. This means that there is no need to track precision for constituents of thePTR_TO_STACKvalues.
Quoted 2 lines
Quoted 1 line
Given above, I think that filtering out r10 should be safe.
Yeah, it makes no sense to track r10. It's always "precise", effectively.
This does make sense. I will craft a patch to fix it (not tracking r10 during precision backtrack) soon.
Quoted 9 lines
Quoted 9 lines
In case if sequence of instructions would be more complex, e.g.:
r9 = r10 if r2 <= r9 goto -1; \
backtrack_insn()would still eventually get to r10 and stop propagation.
Yonghong Song
reviewerPATCH v5 9/17 selftests/bpf: Fix a test_verifier failure
In reply to Yonghong SongThe following test_verifier subtest failed due to
new encoding for BSWAP.
$ ./test_verifier ... #99/u invalid 64-bit BPF_END FAIL Unexpected success to load! verification time 215 usec stack depth 0 processed 3 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 #99/p invalid 64-bit BPF_END FAIL Unexpected success to load! verification time 198 usec stack depth 0 processed 3 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
Tighten the test so it still reports a failure.
--- tools/testing/selftests/bpf/verifier/basic_instr.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
tools/testing/selftests/bpf/verifier/basic_instr.c +3 -3
@@ -176,11 +176,11 @@ .retval = 1, }, { - "invalid 64-bit BPF_END", + "invalid 64-bit BPF_END with BPF_TO_BE", .insns = { BPF_MOV32_IMM(BPF_REG_0, 0), { - .code = BPF_ALU64 | BPF_END | BPF_TO_LE, + .code = BPF_ALU64 | BPF_END | BPF_TO_BE, .dst_reg = BPF_REG_0, .src_reg = 0, .off = 0,
@@ -188,7 +188,7 @@ }, BPF_EXIT_INSN(), }, - .errstr = "unknown opcode d7", + .errstr = "unknown opcode df", .result = REJECT, }, {
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 10/17 selftests/bpf: Add a cpuv4 test runner for cpu=v4 testing
In reply to Yonghong SongSimilar to no-alu32 runner, if clang compiler supports -mcpu=v4, a cpuv4 runner is created to test bpf programs compiled with -mcpu=v4.
The following are some num-of-insn statistics for each newer instructions based on existing selftests, excluding subsequent cpuv4 insn specific tests.
insn pattern # of instructions reg = (s8)reg 4 reg = (s16)reg 4 reg = (s32)reg 144 reg = *(s8 *)(reg + off) 13 reg = *(s16 *)(reg + off) 14 reg = *(s32 *)(reg + off) 15215 reg = bswap16 reg 142 reg = bswap32 reg 38 reg = bswap64 reg 14 reg s/= reg 0 reg s%= reg 0 gotol <offset> 58
Note that in llvm -mcpu=v4 implementation, the compiler is a little bit conservative about generating 'gotol' insn (32-bit branch offset) as it didn't precise count the number of insns (e.g., some insns are debug insns, etc.). Compared to old 'goto' insn, newer 'gotol' insn should have comparable verification states to 'goto' insn.
With current patch set, all selftests passed with -mcpu=v4 when running test_progs-cpuv4 binary. The -mcpu=v3 and -mcpu=v2 run are also successful.
--- tools/testing/selftests/bpf/.gitignore | 2 ++ tools/testing/selftests/bpf/Makefile | 28 ++++++++++++++++++++++---- 2 files changed, 26 insertions(+), 4 deletions(-)
tools/testing/selftests/bpf/.gitignore +2 -0
@@ -13,6 +13,7 @@ test_dev_cgroup /test_progs /test_progs-no_alu32 /test_progs-bpf_gcc +/test_progs-cpuv4 test_verifier_log feature test_sock
@@ -36,6 +37,7 @@ test_cpp *.lskel.h /no_alu32 /bpf_gcc +/cpuv4 /host-tools /tools /runqslower
tools/testing/selftests/bpf/Makefile +24 -4
@@ -33,9 +33,13 @@ CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ LDFLAGS += $(SAN_LDFLAGS) LDLIBS += -lelf -lz -lrt -lpthread -# Silence some warnings when compiled with clang ifneq ($(LLVM),) +# Silence some warnings when compiled with clang CFLAGS += -Wno-unused-command-line-argument +# Check whether cpu=v4 is supported or not by clang +ifneq ($(shell $(CLANG) --target=bpf -mcpu=help 2>&1 | grep 'v4'),) +CLANG_CPUV4 := 1 +endif endif # Order correspond to 'make run_tests' order
@@ -51,6 +55,10 @@ ifneq ($(BPF_GCC),) TEST_GEN_PROGS += test_progs-bpf_gcc endif +ifneq ($(CLANG_CPUV4),) +TEST_GEN_PROGS += test_progs-cpuv4 +endif + TEST_GEN_FILES = test_lwt_ip_encap.bpf.o test_tc_edt.bpf.o TEST_FILES = xsk_prereqs.sh $(wildcard progs/btf_dump_test_case_*.c)
@@ -383,6 +391,11 @@ define CLANG_NOALU32_BPF_BUILD_RULE $(call msg,CLNG-BPF,$(TRUNNER_BINARY),$2) $(Q)$(CLANG) $3 -O2 --target=bpf -c $1 -mcpu=v2 -o $2 endef +# Similar to CLANG_BPF_BUILD_RULE, but with cpu-v4 +define CLANG_CPUV4_BPF_BUILD_RULE + $(call msg,CLNG-BPF,$(TRUNNER_BINARY),$2) + $(Q)$(CLANG) $3 -O2 --target=bpf -c $1 -mcpu=v4 -o $2 +endef # Build BPF object using GCC define GCC_BPF_BUILD_RULE $(call msg,GCC-BPF,$(TRUNNER_BINARY),$2)
@@ -425,7 +438,7 @@ LINKED_BPF_SRCS := $(patsubst %.bpf.o,%.c,$(foreach skel,$(LINKED_SKELS),$($(ske # $eval()) and pass control to DEFINE_TEST_RUNNER_RULES. # Parameters: # $1 - test runner base binary name (e.g., test_progs) -# $2 - test runner extra "flavor" (e.g., no_alu32, gcc-bpf, etc) +# $2 - test runner extra "flavor" (e.g., no_alu32, cpuv4, gcc-bpf, etc) define DEFINE_TEST_RUNNER TRUNNER_OUTPUT := $(OUTPUT)$(if $2,/)$2
@@ -453,7 +466,7 @@ endef # Using TRUNNER_XXX variables, provided by callers of DEFINE_TEST_RUNNER and # set up by DEFINE_TEST_RUNNER itself, create test runner build rules with: # $1 - test runner base binary name (e.g., test_progs) -# $2 - test runner extra "flavor" (e.g., no_alu32, gcc-bpf, etc) +# $2 - test runner extra "flavor" (e.g., no_alu32, cpuv4, gcc-bpf, etc) define DEFINE_TEST_RUNNER_RULES ifeq ($($(TRUNNER_OUTPUT)-dir),)
@@ -584,6 +597,13 @@ TRUNNER_BPF_BUILD_RULE := CLANG_NOALU32_BPF_BUILD_RULE TRUNNER_BPF_CFLAGS := $(BPF_CFLAGS) $(CLANG_CFLAGS) $(eval $(call DEFINE_TEST_RUNNER,test_progs,no_alu32)) +# Define test_progs-cpuv4 test runner. +ifneq ($(CLANG_CPUV4),) +TRUNNER_BPF_BUILD_RULE := CLANG_CPUV4_BPF_BUILD_RULE +TRUNNER_BPF_CFLAGS := $(BPF_CFLAGS) $(CLANG_CFLAGS) +$(eval $(call DEFINE_TEST_RUNNER,test_progs,cpuv4)) +endif + # Define test_progs BPF-GCC-flavored test runner. ifneq ($(BPF_GCC),) TRUNNER_BPF_BUILD_RULE := GCC_BPF_BUILD_RULE
@@ -681,7 +701,7 @@ EXTRA_CLEAN := $(TEST_CUSTOM_PROGS) $(SCRATCH_DIR) $(HOST_SCRATCH_DIR) \ prog_tests/tests.h map_tests/tests.h verifier/tests.h \ feature bpftool \ $(addprefix $(OUTPUT)/,*.o *.skel.h *.lskel.h *.subskel.h \ - no_alu32 bpf_gcc bpf_testmod.ko \ + no_alu32 cpuv4 bpf_gcc bpf_testmod.ko \ liburandom_read.so) .PHONY: docs docs-clean
Signature · 1 line
2.34.1
Re: [PATCH bpf-next v5 10/17] selftests/bpf: Add a cpuv4 test runner for cpu=v4 testing
tools/testing/selftests/bpf/Makefile CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ · line 43
Quoted 10 lines · Yonghong Song
tools/testing/selftests/bpf/Makefile +5
-1-# Silence some warnings when compiled with clang ifneq ($(LLVM),) +# Silence some warnings when compiled with clang CFLAGS += -Wno-unused-command-line-argument +# Check whether cpu=v4 is supported or not by clang +ifneq ($(shell $(CLANG) --target=bpf -mcpu=help 2>&1 | grep 'v4'),) +CLANG_CPUV4 := 1 +endif endif
Gating cpu=v4 testing by LLVM=1 is unnecessary. The kernel can be built by GCC, but we should still build test_progs-cpuv4 when clang supports it.
Please consider a follow up.
I've applied the set, since the rest looks great!
Yonghong Song
reviewerRe: [PATCH bpf-next v5 10/17] selftests/bpf: Add a cpuv4 test runner for cpu=v4 testing
Quoted 16 lines · Alexei Starovoitov
tools/testing/selftests/bpf/Makefile CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ · line 43
Quoted 10 lines · Yonghong Song
tools/testing/selftests/bpf/Makefile +5
-1-# Silence some warnings when compiled with clang ifneq ($(LLVM),) +# Silence some warnings when compiled with clang CFLAGS += -Wno-unused-command-line-argument +# Check whether cpu=v4 is supported or not by clang +ifneq ($(shell $(CLANG) --target=bpf -mcpu=help 2>&1 | grep 'v4'),) +CLANG_CPUV4 := 1 +endif endifGating cpu=v4 testing by LLVM=1 is unnecessary. The kernel can be built by GCC, but we should still build test_progs-cpuv4 when clang supports it.
Quoted 1 line
Please consider a follow up.
Agree. Will do a follow-up for cpu-v4 not depending on LLVM=1.
Quoted 2 lines
I've applied the set, since the rest looks great!
Yonghong Song
reviewerPATCH v5 11/17 selftests/bpf: Add unit tests for new sign-extension load insns
In reply to Yonghong SongAdd unit tests for new ldsx insns. The test includes sign-extension with a single value or with a value range.
If cpuv4 is not supported due to
(1) older compiler, e.g., less than clang version 18, or
(2) test runner test_progs and test_progs-no_alu32 which tests cpu v2 and v3, or
(3) non-x86_64 arch not supporting new insns in jit yet,
a dummy program is added with below output:
#318/1 verifier_ldsx/cpuv4 is not supported by compiler or jit, use a dummy test:OK
#318 verifier_ldsx:OK
to indicate the test passed with a dummy test instead of actually testing cpuv4. I am using a dummy prog to avoid changing the verifier testing infrastructure. Once clang 18 is widely available and other architectures support cpuv4, at least for CI run, the dummy program can be removed.
--- .../selftests/bpf/prog_tests/verifier.c | 2 + .../selftests/bpf/progs/verifier_ldsx.c | 131 ++++++++++++++++++ 2 files changed, 133 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/verifier_ldsx.c
tools/testing/selftests/bpf/prog_tests/verifier.c +2 -0
@@ -31,6 +31,7 @@#include "verifier_int_ptr.skel.h" #include "verifier_jeq_infer_not_null.skel.h" #include "verifier_ld_ind.skel.h" +#include "verifier_ldsx.skel.h" #include "verifier_leak_ptr.skel.h" #include "verifier_loops1.skel.h" #include "verifier_lwt.skel.h"
@@ -133,6 +134,7 @@ void test_verifier_helper_value_access(void) { RUN(verifier_helper_value_accessvoid test_verifier_int_ptr (void ) {RUN (verifier_int_ptr); }void test_verifier_jeq_infer_not_null (void ) {RUN (verifier_jeq_infer_not_null); }void test_verifier_ld_ind (void ) {RUN (verifier_ld_ind); } +void test_verifier_ldsx (void ) {RUN (verifier_ldsx); }void test_verifier_leak_ptr (void ) {RUN (verifier_leak_ptr); }void test_verifier_loops1 (void ) {RUN (verifier_loops1); }void test_verifier_lwt (void ) {RUN (verifier_lwt); }
tools/testing/selftests/bpf/progs/verifier_ldsx.c new file +131 -0
131 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 12/17 selftests/bpf: Add unit tests for new sign-extension mov insns
In reply to Yonghong SongAdd unit tests for movsx insns.
--- .../selftests/bpf/prog_tests/verifier.c | 2 + .../selftests/bpf/progs/verifier_movsx.c | 213 ++++++++++++++++++ 2 files changed, 215 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/verifier_movsx.c
tools/testing/selftests/bpf/prog_tests/verifier.c +2 -0
@@ -41,6 +41,7 @@#include "verifier_map_ret_val.skel.h" #include "verifier_masking.skel.h" #include "verifier_meta_access.skel.h" +#include "verifier_movsx.skel.h" #include "verifier_netfilter_ctx.skel.h" #include "verifier_netfilter_retcode.skel.h" #include "verifier_prevent_map_lookup.skel.h"
@@ -144,6 +145,7 @@ void test_verifier_map_ptr_mixing(void) { RUN(verifier_map_ptr_mixing); }void test_verifier_map_ret_val (void ) {RUN (verifier_map_ret_val); }void test_verifier_masking (void ) {RUN (verifier_masking); }void test_verifier_meta_access (void ) {RUN (verifier_meta_access); } +void test_verifier_movsx (void ) {RUN (verifier_movsx); }void test_verifier_netfilter_ctx (void ) {RUN (verifier_netfilter_ctx); }void test_verifier_netfilter_retcode (void ) {RUN (verifier_netfilter_retcode); }void test_verifier_prevent_map_lookup (void ) {RUN (verifier_prevent_map_lookup); }
tools/testing/selftests/bpf/progs/verifier_movsx.c new file +213 -0
213 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 13/17 selftests/bpf: Add unit tests for new bswap insns
In reply to Yonghong SongAdd unit tests for bswap insns.
--- .../selftests/bpf/prog_tests/verifier.c | 2 + .../selftests/bpf/progs/verifier_bswap.c | 59 +++++++++++++++++++ 2 files changed, 61 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/verifier_bswap.c
tools/testing/selftests/bpf/prog_tests/verifier.c +2 -0
@@ -11,6 +11,7 @@#include "verifier_bounds_deduction_non_const.skel.h" #include "verifier_bounds_mix_sign_unsign.skel.h" #include "verifier_bpf_get_stack.skel.h" +#include "verifier_bswap.skel.h" #include "verifier_btf_ctx_access.skel.h" #include "verifier_cfg.skel.h" #include "verifier_cgroup_inv_retcode.skel.h"
@@ -115,6 +116,7 @@ void test_verifier_bounds_deduction(void) { RUN(verifier_bounds_deduction);void test_verifier_bounds_deduction_non_const (void ) {RUN (verifier_bounds_deduction_non_const); }void test_verifier_bounds_mix_sign_unsign (void ) {RUN (verifier_bounds_mix_sign_unsign); }void test_verifier_bpf_get_stack (void ) {RUN (verifier_bpf_get_stack); } +void test_verifier_bswap (void ) {RUN (verifier_bswap); }void test_verifier_btf_ctx_access (void ) {RUN (verifier_btf_ctx_access); }void test_verifier_cfg (void ) {RUN (verifier_cfg); }void test_verifier_cgroup_inv_retcode (void ) {RUN (verifier_cgroup_inv_retcode); }
tools/testing/selftests/bpf/progs/verifier_bswap.c new file +59 -0
59 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 14/17 selftests/bpf: Add unit tests for new sdiv/smod insns
In reply to Yonghong SongAdd unit tests for sdiv/smod insns.
--- .../selftests/bpf/prog_tests/verifier.c | 2 + .../selftests/bpf/progs/verifier_sdiv.c | 781 ++++++++++++++++++ 2 files changed, 783 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/verifier_sdiv.c
tools/testing/selftests/bpf/prog_tests/verifier.c +2 -0
@@ -54,6 +54,7 @@#include "verifier_ringbuf.skel.h" #include "verifier_runtime_jit.skel.h" #include "verifier_scalar_ids.skel.h" +#include "verifier_sdiv.skel.h" #include "verifier_search_pruning.skel.h" #include "verifier_sock.skel.h" #include "verifier_spill_fill.skel.h"
@@ -159,6 +160,7 @@ void test_verifier_regalloc(void) { RUN(verifier_regalloc); }void test_verifier_ringbuf (void ) {RUN (verifier_ringbuf); }void test_verifier_runtime_jit (void ) {RUN (verifier_runtime_jit); }void test_verifier_scalar_ids (void ) {RUN (verifier_scalar_ids); } +void test_verifier_sdiv (void ) {RUN (verifier_sdiv); }void test_verifier_search_pruning (void ) {RUN (verifier_search_pruning); }void test_verifier_sock (void ) {RUN (verifier_sock); }void test_verifier_spill_fill (void ) {RUN (verifier_spill_fill); }
tools/testing/selftests/bpf/progs/verifier_sdiv.c new file +781 -0
781 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 15/17 selftests/bpf: Add unit tests for new gotol insn
In reply to Yonghong SongAdd unit tests for gotol insn.
--- .../selftests/bpf/prog_tests/verifier.c | 2 + .../selftests/bpf/progs/verifier_gotol.c | 44 +++++++++++++++++++ 2 files changed, 46 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/verifier_gotol.c
tools/testing/selftests/bpf/prog_tests/verifier.c +2 -0
@@ -25,6 +25,7 @@#include "verifier_direct_stack_access_wraparound.skel.h" #include "verifier_div0.skel.h" #include "verifier_div_overflow.skel.h" +#include "verifier_gotol.skel.h" #include "verifier_helper_access_var_len.skel.h" #include "verifier_helper_packet_access.skel.h" #include "verifier_helper_restricted.skel.h"
@@ -131,6 +132,7 @@ void test_verifier_direct_packet_access(void) { RUN(verifier_direct_packet_accesvoid test_verifier_direct_stack_access_wraparound (void ) {RUN (verifier_direct_stack_access_wraparound); }void test_verifier_div0 (void ) {RUN (verifier_div0); }void test_verifier_div_overflow (void ) {RUN (verifier_div_overflow); } +void test_verifier_gotol (void ) {RUN (verifier_gotol); }void test_verifier_helper_access_var_len (void ) {RUN (verifier_helper_access_var_len); }void test_verifier_helper_packet_access (void ) {RUN (verifier_helper_packet_access); }void test_verifier_helper_restricted (void ) {RUN (verifier_helper_restricted); }
tools/testing/selftests/bpf/progs/verifier_gotol.c new file +44 -0
44 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 16/17 selftests/bpf: Test ldsx with more complex cases
In reply to Yonghong SongThe following ldsx cases are tested:
- signed readonly map value
- read/write map value
- probed memory
- not-narrowed ctx field access
- narrowed ctx field access.
Without previous proper verifier/git handling, the test will fail.
If cpuv4 is not supported either by compiler or by jit, the test will be skipped.
# ./test_progs -t ldsx_insn #113/1 ldsx_insn/map_val and probed_memory:SKIP #113/2 ldsx_insn/ctx_member_sign_ext:SKIP #113/3 ldsx_insn/ctx_member_narrow_sign_ext:SKIP #113 ldsx_insn:SKIP Summary: 1/0 PASSED, 3 SKIPPED, 0 FAILED
--- .../selftests/bpf/bpf_testmod/bpf_testmod.c | 9 +- .../selftests/bpf/prog_tests/test_ldsx_insn.c | 139 ++++++++++++++++++ .../selftests/bpf/progs/test_ldsx_insn.c | 118 +++++++++++++++ 3 files changed, 265 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/bpf/prog_tests/test_ldsx_insn.c create mode 100644 tools/testing/selftests/bpf/progs/test_ldsx_insn.c
tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c +8 -1
@@ -98,6 +98,12 @@ bpf_testmod_test_struct_arg_8(u64 a, void *b, short c, int d, void *e,return bpf_testmod_test_struct_arg_result; } +noinline int +bpf_testmod_test_arg_ptr_to_struct (struct bpf_testmod_struct_arg_1 *a) { + bpf_testmod_test_struct_arg_result = a->a; +return bpf_testmod_test_struct_arg_result; +} + __bpf_kfunc voidbpf_testmod_test_mod_kfunc (int i) {
@@ -240,7 +246,7 @@ bpf_testmod_test_read(struct file *file, struct kobject *kobj, .off = off, .len = len, }; -struct bpf_testmod_struct_arg_1 struct_arg1 = {10 }; +struct bpf_testmod_struct_arg_1 struct_arg1 = {10 }, struct_arg1_2 = {-1 };struct bpf_testmod_struct_arg_2 struct_arg2 = {2 ,3 };struct bpf_testmod_struct_arg_3 *struct_arg3;struct bpf_testmod_struct_arg_4 struct_arg4 = {21 ,22 };
@@ -259,6 +265,7 @@ bpf_testmod_test_read(struct file *file, struct kobject *kobj, (void )bpf_testmod_test_struct_arg_8 (16 , (void *)17 ,18 ,19 , (void *)20 , struct_arg4,23 ); + (void )bpf_testmod_test_arg_ptr_to_struct (&struct_arg1_2); struct_arg3 =kmalloc ((sizeof (struct bpf_testmod_struct_arg_3 ) +sizeof (int )),GFP_KERNEL );
tools/testing/selftests/bpf/prog_tests/test_ldsx_insn.c new file +139 -0
139 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_ldsx_insn.c new file +118 -0
118 lines not on this page · raw message
Signature · 1 line
2.34.1
Yonghong Song
reviewerPATCH v5 17/17 docs/bpf: Add documentation for new instructions
In reply to Yonghong SongAdd documentation in instruction-set.rst for new instruction encoding and their corresponding operations. Also removed the question related to 'no BPF_SDIV' in bpf_design_QA.rst since we have BPF_SDIV insn now.
--- Documentation/bpf/bpf_design_QA.rst | 5 - .../bpf/standardization/instruction-set.rst | 115 ++++++++++++------ 2 files changed, 79 insertions(+), 41 deletions(-)
Documentation/bpf/bpf_design_QA.rst +0 -5
@@ -140,11 +140,6 @@ A: Because if we picked one-to-one relationship to x64 it would have made it more complicated to support on arm64 and other archs. Also it needs div-by-zero runtime check. -Q: Why there is no BPF_SDIV for signed divide operation? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -A: Because it would be rarely used. llvm errors in such case and -prints a suggestion to use unsigned divide instead. - Q: Why BPF has implicit prologue and epilogue? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A: Because architectures like sparc have register windows and in general
Documentation/bpf/standardization/instruction-set.rst +79 -36
169 lines not on this page · raw message
Signature · 1 line
2.34.1
David Vernet
reviewerRe: [PATCH bpf-next v5 17/17] docs/bpf: Add documentation for new instructions
Quoted 4 lines · Yonghong Song
Add documentation in
instruction-set.rstfor new instruction encoding and their corresponding operations. Also removed the question related to 'noBPF_SDIV' inbpf_design_QA.rstsince we haveBPF_SDIVinsn now.
Sorry for reviewing this after it was merged. Leaving some thoughts which can be addressed in a subsequent patch.
Quoted 61 lines
Signed-off-by Yonghong Song <[email protected]>--- Documentation/bpf/bpf_design_QA.rst | 5 - .../bpf/standardization/instruction-set.rst | 115 ++++++++++++------ 2 files changed, 79 insertions(+), 41 deletions(-)Documentation/bpf/bpf_design_QA.rst +0
-5@@ -140,11 +140,6 @@ A: Because if we picked one-to-one relationship to x64 it would have made it more complicated to support on arm64 and other archs. Also it needs div-by-zero runtime check. -Q: Why there is no BPF_SDIV for signed divide operation? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -A: Because it would be rarely used. llvm errors in such case and -prints a suggestion to use unsigned divide instead. - Q: Why BPF has implicit prologue and epilogue? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A: Because architectures like sparc have register windows and in generalDocumentation/bpf/standardization/instruction-set.rst +11
-18@@ -154,24 +154,27 @@ otherwise identical operations. The 'code' field encodes the operation as below, where 'src' and 'dst' refer to the values of the source and destination registers, respectively. -======== ===== ========================================================== -code value description -======== ===== ========================================================== -BPF_ADD 0x00 dst += src -BPF_SUB 0x10 dst -= src -BPF_MUL 0x20 dst \*= src -BPF_DIV 0x30 dst = (src != 0) ? (dst / src) : 0 -BPF_OR 0x40 dst \|= src -BPF_AND 0x50 dst &= src -BPF_LSH 0x60 dst <<= (src & mask) -BPF_RSH 0x70 dst >>= (src & mask) -BPF_NEG 0x80 dst = -dst -BPF_MOD 0x90 dst = (src != 0) ? (dst % src) : dst -BPF_XOR 0xa0 dst ^= src -BPF_MOV 0xb0 dst = src -BPF_ARSH 0xc0 sign extending dst >>= (src & mask) -BPF_END 0xd0 byte swap operations (see `Byte swap instructions`_ below) -======== ===== ========================================================== +======== ===== ======= ========================================================== +code value offset description +======== ===== ======= ========================================================== +BPF_ADD 0x00 0 dst += src +BPF_SUB 0x10 0 dst -= src +BPF_MUL 0x20 0 dst \*= src +BPF_DIV 0x30 0 dst = (src != 0) ? (dst / src) : 0 +BPF_SDIV 0x30 1 dst = (src != 0) ? (dst s/ src) : 0 +BPF_OR 0x40 0 dst \|= src +BPF_AND 0x50 0 dst &= src +BPF_LSH 0x60 0 dst <<= (src & mask)
Documentation/bpf/standardization/instruction-set.rst otherwise identical operations. · line 177
Quoted 10 lines
Documentation/bpf/standardization/instruction-set.rst +10
-0+BPF_RSH 0x70 0 dst >>= (src & mask) +BPF_NEG 0x80 0 dst = -dst +BPF_MOD 0x90 0 dst = (src != 0) ? (dst % src) : dst +BPF_SMOD 0x90 1 dst = (src != 0) ? (dst s% src) : dst +BPF_XOR 0xa0 0 dst ^= src +BPF_MOV 0xb0 0 dst = src +BPF_MOVSX 0xb0 8/16/32 dst = (s8,s16,s32)src +BPF_ARSH 0xc0 0 sign extending dst >>= (src & mask) +BPF_END 0xd0 0 byte swap operations (see `Byte swap instructions`_ below) +======== ===== ============ ==========================================================
Looks like the alignment is off here.
Quoted 4 lines
Documentation/bpf/standardization/instruction-set.rst +0
-0Underflow and overflow are allowed during arithmetic operations, meaning the 64-bit or 32-bit value will wrap. If eBPF program execution would
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 205
Quoted 10 lines
Documentation/bpf/standardization/instruction-set.rst +2
-5@@ -198,11 +201,20 @@ where '(u32)' indicates that the upper 32 bits are zeroed. dst = dst ^ imm32 -Also note that the division and modulo operations are unsigned. Thus, for -``BPF_ALU``, 'imm' is first interpreted as an unsigned 32-bit value, whereas -for ``BPF_ALU64``, 'imm' is first sign extended to 64 bits and the result -interpreted as an unsigned 64-bit value. There are no instructions for -signed division or modulo. +Note that most instructions have instruction offset of 0. But three instructions +(BPF_SDIV, BPF_SMOD, BPF_MOVSX) have non-zero offset.
Can we be consistent with where we apply ``<code>``? It we're going to e.g. apply it to ``BPF_ALU`` below, we should apply it here as well (note that there are a couple small grammatical changes as well):
Note that most instructions have an offset of 0. Only three instructions (``BPF_SDIV``, ``BPF_SMOD``, ``BPF_MOVSX``) have a non-zero offset.
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 210
Quoted 5 lines
Documentation/bpf/standardization/instruction-set.rst +5
-0+ +The devision and modulo operations support both unsigned and signed flavors. +For unsigned operation (BPF_DIV and BPF_MOD), for ``BPF_ALU``, 'imm' is first +interpreted as an unsigned 32-bit value, whereas for ``BPF_ALU64``, 'imm' is +first sign extended to 64 bits and the result interpreted as an unsigned 64-bit
I prefer the form of how you described the BPF_SDIV and BPF_SMOD instructions below. Can we use that for BPF_DIV / BPD_MOD, i.e.:
For unsigned operations (``BPF_DIV`` and ``BPF_MOD``), for ``BPF_ALU``, 'imm' is interpreted as a 32-bit unsigned value. For ``BPF_ALU64``, 'imm' is first sign extended from 32 to 64 bits, and then interpreted as a 64-bit unsigned value.
/B
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 211
Quoted 1 line
Documentation/bpf/standardization/instruction-set.rst +1
-0+value. For signed operation (BPF_SDIV and BPF_SMOD), for ``BPF_ALU``, 'imm' is
Same suggestion as above (``, and s/operation/operations)
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 213
Quoted 2 lines
Documentation/bpf/standardization/instruction-set.rst +2
-0+interpreted as a signed value. For ``BPF_ALU64``, the 'imm' is sign extended +from 32 to 64 and interpreted as a signed 64-bit value.
Also suggest a slight modification to exactly match the form of the unsigned description:
For signed operations (``BPF_SDIV`` and ``BPF_SMOD``), for ``BPF_ALU``, 'imm' is interpreted as a 32-bit signed value. For ``BPF_ALU64``, 'imm' is first sign extended from 32 to 64 bits, and then interpreted as a 64-bit signed value.
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 215
Quoted 2 lines
Documentation/bpf/standardization/instruction-set.rst +2
-0+ +Instruction BPF_MOVSX does move operation with sign extension.
The ``BPF_MOVSX`` instruction does a move operation with sign extension.
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 216
Quoted 1 line
Documentation/bpf/standardization/instruction-set.rst +1
-0+``BPF_ALU | MOVSX`` sign extendes 8-bit and 16-bit into 32-bit and upper 32-bit are zeroed.
``BPF_ALU | BPF_MOVSX`` sign extends 8-bit and 16-bit operands into 32 bit operands, and zeroes the remaining upper 32 bits.
Documentation/bpf/standardization/instruction-set.rst where '(u32)' indicates that the upper 32 bits are zeroed. · line 217
Quoted 1 line
Documentation/bpf/standardization/instruction-set.rst +1
-0+``BPF_ALU64 | MOVSX`` sign extends 8-bit, 16-bit and 32-bit into 64-bit.
``BPF_ALU64 | BPF_MOVSX`` sign extends 8-bit, 16-bit, and 32-bit operands into 64 bit operands.
Documentation/bpf/standardization/instruction-set.rst for 32-bit operations. · line 223
Quoted 6 lines
Documentation/bpf/standardization/instruction-set.rst +0
-0Shift operations use a mask of 0x3F (63) for 64-bit operations and 0x1F (31) for 32-bit operations.@@ -210,21 +222,23 @@ for 32-bit operations. Byte swap instructions ~~~~~~~~~~~~~~~~~~~~~~
Not your change, but this underline should be converted to ----- to match the other instruction type sections.
Quoted 4 lines
Documentation/bpf/standardization/instruction-set.rst +1
-2-The byte swap instructions use an instruction class of ``BPF_ALU`` and a 4-bit -'code' field of ``BPF_END``. +The byte swap instructions use instruction classes of ``BPF_ALU`` and ``BPF_ALU64``
Documentation/bpf/standardization/instruction-set.rst for 32-bit operations. · line 233
Quoted 10 lines
Documentation/bpf/standardization/instruction-set.rst +4
-2+and a 4-bit 'code' field of ``BPF_END``. The byte swap instructions operate on the destination register only and do not use a separate source register or immediate value. -The 1-bit source operand field in the opcode is used to select what byte -order the operation convert from or to: +For ``BPF_ALU``, the 1-bit source operand field in the opcode is used to select what byte +order the operation convert from or to. For ``BPF_ALU64``, the 1-bit source operand +field in the opcode is not used and must be 0.
For ``BPF_ALU``, the 1-bit source operand field in the opcode is used to select what byte order the operation converts from or to. For ``BPF_ALU64``, the 1-bit source operand field in the opcode is reserved and must be set to 0.
Documentation/bpf/standardization/instruction-set.rst for 32-bit operations. · line 240
Quoted 12 lines
Documentation/bpf/standardization/instruction-set.rst +6
-6-========= ===== ================================================= -source value description -========= ===== ================================================= -BPF_TO_LE 0x00 convert between host byte order and little endian -BPF_TO_BE 0x08 convert between host byte order and big endian -========= ===== ================================================= +========= ========= ===== ================================================= +class source value description +========= ========= ===== ================================================= +BPF_ALU BPF_TO_LE 0x00 convert between host byte order and little endian +BPF_ALU BPF_TO_BE 0x08 convert between host byte order and big endian +BPF_ALU64 BPF_TO_LE 0x00 do byte swap unconditionally
Should we say "Unused" or "Reserved" for BPF_ALU64 rather than BPF_TO_LE?
Quoted 30 lines
Documentation/bpf/standardization/instruction-set.rst +9
-1+========= ========= ===== ================================================= The 'imm' field encodes the width of the swap operations. The following widths are supported: 16, 32 and 64.@@ -239,6 +253,12 @@ Examples: dst = htobe64(dst) +``BPF_ALU64 | BPF_TO_LE | BPF_END`` with imm = 16/32/64 means:: + + dst = bswap16 dst + dst = bswap32 dst + dst = bswap64 dst + Jump instructions -----------------@@ -249,7 +269,8 @@ The 'code' field encodes the operation as below: ======== ===== === =========================================== ========================================= code value src description notes ======== ===== === =========================================== ========================================= -BPF_JA 0x0 0x0 PC += offset BPF_JMP only +BPF_JA 0x0 0x0 PC += offset BPF_JMP class +BPF_JA 0x0 0x0 PC += imm BPF_JMP32 class BPF_JEQ 0x1 any PC += offset if dst == src BPF_JGT 0x2 any PC += offset if dst > src unsigned BPF_JGE 0x3 any PC += offset if dst >= src unsigned@@ -278,6 +299,16 @@ Example: where 's>=' indicates a signed '>=' comparison.
Documentation/bpf/standardization/instruction-set.rst Example: · line 310
Quoted 10 lines
Documentation/bpf/standardization/instruction-set.rst +9
-0+``BPF_JA | BPF_K | BPF_JMP32`` (0x06) means:: + + gotol +imm + +where 'imm' means the branch offset comes from insn 'imm' field. + +Note there are two flavors of BPF_JA instrions. BPF_JMP class permits 16-bit jump offset while +BPF_JMP32 permits 32-bit jump offset. A >16bit conditional jmp can be converted to a <16bit +conditional jmp plus a 32-bit unconditional jump.
Note that there are two flavors of ``BPF_JA`` instructions. The ``BPF_JMP`` class permits a 16-bit jump offset specified by 'offset' field, whereas the ``BPF_JMP32`` class permits a 32-bit jump offset specified by the 'imm' field. A > 16-bit conditional jump may be converted to a < 16-bit conditional jump plus a 32-bit unconditional jump.
Quoted 13 lines
Documentation/bpf/standardization/instruction-set.rst +2
-0+ Helper functions ~~~~~~~~~~~~~~~~@@ -320,6 +351,7 @@ The mode modifier is one of: BPF_ABS 0x20 legacy BPF packet access (absolute) `Legacy BPF Packet access instructions`_ BPF_IND 0x40 legacy BPF packet access (indirect) `Legacy BPF Packet access instructions`_ BPF_MEM 0x60 regular load and store operations `Regular load and store operations`_ + BPF_MEMSX 0x80 sign-extension load operations `Sign-extension load operations`_ BPF_ATOMIC 0xc0 atomic operations `Atomic operations`_ ============= ===== ==================================== =============
Documentation/bpf/standardization/instruction-set.rst instructions that transfer data between a register and memory. · line 388
Quoted 8 lines
Documentation/bpf/standardization/instruction-set.rst +4
-1@@ -350,9 +382,20 @@ instructions that transfer data between a register and memory. ``BPF_MEM | <size> | BPF_LDX`` means:: - dst = *(size *) (src + offset) + dst = *(unsigned size *) (src + offset) + +Where size is one of: ``BPF_B``, ``BPF_H``, ``BPF_W``, or ``BPF_DW`` and +'unsigned size' is one of u8, u16, u32 and u64.
s/and/or
Documentation/bpf/standardization/instruction-set.rst instructions that transfer data between a register and memory. · line 398
Quoted 11 lines
Documentation/bpf/standardization/instruction-set.rst +9
-1+ +The ``BPF_MEMSX`` mode modifier is used to encode sign-extension load +instructions that transfer data between a register and memory. + +``BPF_MEMSX | <size> | BPF_LDX`` means:: + + dst = *(signed size *) (src + offset) -Where size is one of: ``BPF_B``, ``BPF_H``, ``BPF_W``, or ``BPF_DW``. +Where size is one of: ``BPF_B``, ``BPF_H`` or ``BPF_W``, and +'signed size' is one of s8, s16 and s32.
s/and/or
Quoted 7 lines
Documentation/bpf/standardization/instruction-set.rst +0
-0Atomic operations -----------------Signature · 1 line
2.34.1
Yonghong Song
reviewerRe: [PATCH bpf-next v5 17/17] docs/bpf: Add documentation for new instructions
Quoted 8 lines · David Vernet
Quoted 4 lines · Yonghong Song
Add documentation in
instruction-set.rstfor new instruction encoding and their corresponding operations. Also removed the question related to 'noBPF_SDIV' inbpf_design_QA.rstsince we haveBPF_SDIVinsn now.Sorry for reviewing this after it was merged. Leaving some thoughts which can be addressed in a subsequent patch.
Thanks David. Ack to your below suggestions.
Will send a patch later on to address your below comments.
Quoted 9 lines
Quoted 9 lines
Signed-off-by Yonghong Song <[email protected]>--- Documentation/bpf/bpf_design_QA.rst | 5 - .../bpf/standardization/instruction-set.rst | 115 ++++++++++++------ 2 files changed, 79 insertions(+), 41 deletions(-)
[...]
This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <[email protected]>:
Hello:
This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <[email protected]>:
Quoted 11 lines · On Thu, 27 Jul 2023 18:11:43 -0700 you wrote:
In previous discussion ([1]), it is agreed that we should introduce cpu version 4 (llvm flag -mcpu=v4) which contains some instructions which can simplify code, make code easier to understand, fix the existing problem, or simply for feature completeness. More specifically, the following new insns are proposed:
. sign extended load
. sign extended mov
. bswap
. signed div/mod
. ja with 32-bit offset
Quoted 1 line
[...]
Here is the summary with links:
- [bpf-next,v5,01/17] bpf: Support new sign-extension load insns
https://git.kernel.org/bpf/bpf-next/c/1f9a1ea821ff - [bpf-next,v5,02/17] bpf: Support new sign-extension mov insns https://git.kernel.org/bpf/bpf-next/c/8100928c8814 - [bpf-next,v5,03/17] bpf: Handle sign-extenstin ctx member accesses https://git.kernel.org/bpf/bpf-next/c/1f1e864b6555 - [bpf-next,v5,04/17] bpf: Support new unconditional bswap instruction https://git.kernel.org/bpf/bpf-next/c/0845c3db7bf5 - [bpf-next,v5,05/17] bpf: Support new signed div/mod instructions. https://git.kernel.org/bpf/bpf-next/c/ec0e2da95f72 - [bpf-next,v5,06/17] bpf: Fix jit blinding with new sdiv/smov insns https://git.kernel.org/bpf/bpf-next/c/7058e3a31ee4 - [bpf-next,v5,07/17] bpf: Support new 32bit offset jmp instruction https://git.kernel.org/bpf/bpf-next/c/4cd58e9af8b9 - [bpf-next,v5,09/17] selftests/bpf: Fix a test_verifier failure https://git.kernel.org/bpf/bpf-next/c/86180493a2ef - [bpf-next,v5,10/17] selftests/bpf: Add a cpuv4 test runner for cpu=v4 testing https://git.kernel.org/bpf/bpf-next/c/a5d0c26a2784 - [bpf-next,v5,11/17] selftests/bpf: Add unit tests for new sign-extension load insns https://git.kernel.org/bpf/bpf-next/c/147c8f4470ee - [bpf-next,v5,12/17] selftests/bpf: Add unit tests for new sign-extension mov insns https://git.kernel.org/bpf/bpf-next/c/f02ec3ff3f09 - [bpf-next,v5,13/17] selftests/bpf: Add unit tests for new bswap insns https://git.kernel.org/bpf/bpf-next/c/79dbabc17540 - [bpf-next,v5,14/17] selftests/bpf: Add unit tests for new sdiv/smod insns https://git.kernel.org/bpf/bpf-next/c/de1c26809ec3 - [bpf-next,v5,15/17] selftests/bpf: Add unit tests for new gotol insn https://git.kernel.org/bpf/bpf-next/c/613dad498072 - [bpf-next,v5,16/17] selftests/bpf: Test ldsx with more complex cases https://git.kernel.org/bpf/bpf-next/c/0c606571ae07 - [bpf-next,v5,17/17] docs/bpf: Add documentation for new instructions https://git.kernel.org/bpf/bpf-next/c/245d4c40c09b
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html