Searched refs:changes_pkt_data (Results 1 – 9 of 9) sorted by relevance
57 subprog->changes_pkt_data = true; in mark_subprog_changes_pkt_data()88 caller->changes_pkt_data |= callee->changes_pkt_data; in merge_callee_effects()677 env->prog->aux->changes_pkt_data = env->subprog_info[0].changes_pkt_data; in bpf_check_cfg()
1223 func[i]->aux->changes_pkt_data = env->subprog_info[i].changes_pkt_data; in jit_subprogs()
9758 sub->changes_pkt_data) { in btf_check_func_arg_match() 9980 if (env->subprog_info[subprog].changes_pkt_data) in check_func_call() 20199 ? aux->func[subprog]->aux->changes_pkt_data in bpf_check_attach_target() 20200 : aux->changes_pkt_data; in bpf_check_attach_target() 20201 if (prog->aux->changes_pkt_data && !tgt_changes_pkt_data) { in bpf_check_attach_target()
828 bool changes_pkt_data: 1; member
1818 bool changes_pkt_data;1781 bool changes_pkt_data; global() member
1526 prog->aux->changes_pkt_data) in sock_map_prog_attach_check()