On Wed, Jun 8, 2022 at 12:27 PM Eduard Zingerman <eddyz87@xxxxxxxxx> wrote: > > Allows to specify expected and unexpected instruction sequences in > test_verifier test cases. The instructions are requested from kernel > after BPF program loading, thus allowing to check some of the > transformations applied by BPF verifier. > > - `expected_insn` field specifies a sequence of instructions expected > to be found in the program; > - `unexpected_insn` field specifies a sequence of instructions that > are not expected to be found in the program; > - `INSN_OFF_MASK` and `INSN_IMM_MASK` values could be used to mask > `off` and `imm` fields. > - `SKIP_INSNS` could be used to specify that some instructions in the > (un)expected pattern are not important (behavior similar to usage of > `\t` in `errstr` field). > > The intended usage is as follows: > [...] > > Here it is expected that move of 1 to register 1 would remain in place > and helper function call instruction would be replaced by a relative > call instruction. > > Signed-off-by: Eduard Zingerman <eddyz87@xxxxxxxxx> Acked-by: Song Liu <songliubraving@xxxxxx>
