Searched refs:BPF_SIG_VERIFIED (Results 1 – 4 of 4) sorted by relevance
155 yields ``BPF_SIG_VERIFIED`` and the program loads. This is the ordinary case194 BPF_SIG_VERIFIED,197 ``BPF_SIG_VERIFIED`` means the signature is valid and covers the instructions208 recorded with a weaker verdict. ``BPF_SIG_VERIFIED`` therefore always means the235 kernel. For a signed load the verdict is ``BPF_SIG_VERIFIED`` here (the signature246 ``BPF_SIG_VERIFIED`` *here* means only "validly signed" - not "loaded". Allowing254 (``security_bpf_prog()``), does ``BPF_SIG_VERIFIED`` carry its full meaning:294 if (verdict != BPF_SIG_VERIFIED)326 - ``verdict == BPF_SIG_VERIFIED`` *here* means **fully** verified - a program363 if (prog->aux->sig.verdict != BPF_SIG_VERIFIED)[all …]
26 BPF_SIG_VERIFIED, enumerator1295 ASSERT_EQ(lsm->bss->sig_verdict, BPF_SIG_VERIFIED, in lsm_signature_verdict()1327 ASSERT_EQ(lsm->bss->sig_verdict, BPF_SIG_VERIFIED, in lsm_signature_verdict()
1729 BPF_SIG_VERIFIED, enumerator
18725 env->prog->aux->sig.verdict == BPF_SIG_VERIFIED) { in __add_used_map()20967 prog->aux->sig.verdict = BPF_SIG_VERIFIED; in bpf_prog_verify_signature()