Re: [PATCH RFC v2 net-next 10/16] bpf: add eBPF verifier

On Thu, Jul 17, 2014 at 9:20 PM, Alexei Starovoitov [off-list ref] wrote:

Safety of eBPF programs is statically determined by the verifier, which detects:
- loops
- out of range jumps
- unreachable instructions
- invalid instructions
- uninitialized register access
- uninitialized stack access
- misaligned stack access
- out of range stack access
- invalid calling convention

Is there something that documents exactly what conditions an eBPF
program must satisfy in order to be considered valid?

--Andy