Searched refs:verifier (Results 1 – 3 of 3) sorted by relevance
51 mod verifier; module118 verifier: Verifier, field144 verifier::check(prog)?; in new()149 verifier: verifier::check, in new()178 (self.verifier)(prog)?; in set_program()213 pub fn set_verifier(&mut self, verifier: Verifier) -> Result<(), Error> { in set_verifier()215 verifier(prog)?; in set_verifier()217 self.verifier = verifier; in set_verifier()712 pub fn set_verifier(&mut self, verifier: Verifier) -> Result<(), Error> { in set_verifier()713 self.parent.set_verifier(verifier) in set_verifier()[all …]
2 mod verifier; module7 use crate::bpf::prog::verifier::BpfProgVerifier;
162 checked with a very simple verifier (nothing close to the one for Linux163 kernel). Users are also able to replace it with a custom verifier.184 verifier attached to the VM. The verifying function of the VM can be changed at191 verifier: Verifier) -> Result<(), Error>195 verifier also immediately runs it on the loaded program. However, the verifier657 The ”verifier” of this crate is very short and has nothing to do with the658 kernel verifier, which means that it accepts programs that may not be safe. On660 crash your system. Implementing a verifier similar to the one in the kernel is696 * Improve verifier. Could we find a way to directly support programs compiled