Home
last modified time | relevance | path

Searched refs:PTR_TO_CTX (Results 1 – 2 of 2) sorted by relevance

/linux-4.1.27/kernel/bpf/
Dverifier.c132 PTR_TO_CTX, /* reg points to bpf_context */ enumerator
232 [PTR_TO_CTX] = "ctx",
476 regs[BPF_REG_1].type = PTR_TO_CTX; in init_reg_state()
547 state->regs[value_regno].type == PTR_TO_CTX)) { in check_stack_write()
665 } else if (state->regs[regno].type == PTR_TO_CTX) { in check_mem_access()
777 expected_type = PTR_TO_CTX; in check_func_arg()
1240 if (regs[BPF_REG_6].type != PTR_TO_CTX) { in check_ld_abs()
1674 (src_reg_type == PTR_TO_CTX || in do_check()
1675 insn->imm == PTR_TO_CTX)) { in do_check()
1971 if (insn->imm != PTR_TO_CTX) { in convert_ctx_accesses()
/linux-4.1.27/Documentation/networking/
Dfilter.txt1018 and has type PTR_TO_CTX.
1020 PTR_TO_CTX as well and can be used on the right hand side of expression.
1021 If R1=PTR_TO_CTX and insn is R2=R1+R1, then R2=UNKNOWN_VALUE,
1043 are PTR_TO_CTX, PTR_TO_MAP, FRAME_PTR. They are bounds and alignment checked.
1052 At the start R1 type is PTR_TO_CTX (a pointer to generic 'struct bpf_context')
1059 If R6=PTR_TO_CTX, via is_valid_access() callback the verifier will know