Re: [bpf-next PATCH v3 08/18] bpf: sk_msg program helper bpf_sk_msg_pull_data

2018-03-19 Thread John Fastabend
On 03/19/2018 01:24 PM, Alexei Starovoitov wrote: > On Sun, Mar 18, 2018 at 12:57:25PM -0700, John Fastabend wrote: >> Currently, if a bpf sk msg program is run the program >> can only parse data that the (start,end) pointers already >> consumed. For sendmsg hooks this is likely the first >> scatte

Re: [bpf-next PATCH v3 08/18] bpf: sk_msg program helper bpf_sk_msg_pull_data

2018-03-19 Thread Alexei Starovoitov
On Sun, Mar 18, 2018 at 12:57:25PM -0700, John Fastabend wrote: > Currently, if a bpf sk msg program is run the program > can only parse data that the (start,end) pointers already > consumed. For sendmsg hooks this is likely the first > scatterlist element. For sendpage this will be the range > (0,

Re: [bpf-next PATCH v3 08/18] bpf: sk_msg program helper bpf_sk_msg_pull_data

2018-03-18 Thread David Miller
From: John Fastabend Date: Sun, 18 Mar 2018 12:57:25 -0700 > Currently, if a bpf sk msg program is run the program > can only parse data that the (start,end) pointers already > consumed. For sendmsg hooks this is likely the first > scatterlist element. For sendpage this will be the range > (0,0)

[bpf-next PATCH v3 08/18] bpf: sk_msg program helper bpf_sk_msg_pull_data

2018-03-18 Thread John Fastabend
Currently, if a bpf sk msg program is run the program can only parse data that the (start,end) pointers already consumed. For sendmsg hooks this is likely the first scatterlist element. For sendpage this will be the range (0,0) because the data is shared with userspace and by default we want to avo