Re: [PATCH net-next] bpf: fix loading of BPF_MAXINSNS sized programs

2016-12-07 Thread David Miller
From: Daniel Borkmann Date: Wed, 7 Dec 2016 01:15:44 +0100 > General assumption is that single program can hold up to BPF_MAXINSNS, > that is, 4096 number of instructions. It is the case with cBPF and > that limit was carried over to eBPF. When recently testing digest, I >

Re: [PATCH net-next] bpf: fix loading of BPF_MAXINSNS sized programs

2016-12-07 Thread Daniel Borkmann
On 12/07/2016 10:42 AM, Sergei Shtylyov wrote: Hello! On 12/7/2016 3:15 AM, Daniel Borkmann wrote: General assumption is that single program can hold up to BPF_MAXINSNS, that is, 4096 number of instructions. It is the case with cBPF and Up to BPF_MAXINSNS (that is 4096) instructions.

Re: [PATCH net-next] bpf: fix loading of BPF_MAXINSNS sized programs

2016-12-07 Thread Sergei Shtylyov
Hello! On 12/7/2016 3:15 AM, Daniel Borkmann wrote: General assumption is that single program can hold up to BPF_MAXINSNS, that is, 4096 number of instructions. It is the case with cBPF and Up to BPF_MAXINSNS (that is 4096) instructions. that limit was carried over to eBPF. When

[PATCH net-next] bpf: fix loading of BPF_MAXINSNS sized programs

2016-12-06 Thread Daniel Borkmann
General assumption is that single program can hold up to BPF_MAXINSNS, that is, 4096 number of instructions. It is the case with cBPF and that limit was carried over to eBPF. When recently testing digest, I noticed that it's actually not possible to feed 4096 instructions via bpf(2). The check