Re: pull-request: bpf-next 2017-12-18

2017-12-22 Thread Daniel Borkmann
On 12/22/2017 03:42 PM, David Miller wrote: > From: Daniel Borkmann > Date: Fri, 22 Dec 2017 00:48:22 +0100 > >> Looks good, one thing: If I spot this correctly, isn't here a ... >> >> prog->aux->jit_data = jit_data; >> >> ... missing? Otherwise the context

Re: pull-request: bpf-next 2017-12-18

2017-12-22 Thread David Miller
From: Daniel Borkmann Date: Fri, 22 Dec 2017 00:48:22 +0100 > Looks good, one thing: If I spot this correctly, isn't here a ... > > prog->aux->jit_data = jit_data; > > ... missing? Otherwise the context from the initial pass is neither > saved for the extra

Re: pull-request: bpf-next 2017-12-18

2017-12-21 Thread Daniel Borkmann
On 12/21/2017 05:28 PM, David Miller wrote: > From: David Miller > Date: Wed, 20 Dec 2017 16:16:44 -0500 (EST) > >> I think I understand how this new stuff works, I'll take a stab at >> doing the sparc64 JIT bits. > > This patch should do it, please queue up for bpf-next. >

Re: pull-request: bpf-next 2017-12-18

2017-12-21 Thread David Miller
From: David Miller Date: Wed, 20 Dec 2017 16:16:44 -0500 (EST) > I think I understand how this new stuff works, I'll take a stab at > doing the sparc64 JIT bits. This patch should do it, please queue up for bpf-next. But this is really overkill on sparc64. No matter where

Re: pull-request: bpf-next 2017-12-18

2017-12-20 Thread David Miller
From: Alexei Starovoitov Date: Mon, 18 Dec 2017 22:28:30 -0800 > On Mon, Dec 18, 2017 at 10:51:53AM -0500, David Miller wrote: >> From: Daniel Borkmann >> Date: Mon, 18 Dec 2017 01:33:07 +0100 >> >> > The following pull-request contains BPF

Re: pull-request: bpf-next 2017-12-18

2017-12-18 Thread Alexei Starovoitov
On Mon, Dec 18, 2017 at 10:51:53AM -0500, David Miller wrote: > From: Daniel Borkmann > Date: Mon, 18 Dec 2017 01:33:07 +0100 > > > The following pull-request contains BPF updates for your *net-next* tree. > > > > The main changes are: > > > > 1) Allow arbitrary function

Re: pull-request: bpf-next 2017-12-18

2017-12-18 Thread David Miller
From: Daniel Borkmann Date: Mon, 18 Dec 2017 01:33:07 +0100 > The following pull-request contains BPF updates for your *net-next* tree. > > The main changes are: > > 1) Allow arbitrary function calls from one BPF function to another BPF > function. >As of today when

pull-request: bpf-next 2017-12-18

2017-12-17 Thread Daniel Borkmann
Hi David, The following pull-request contains BPF updates for your *net-next* tree. The main changes are: 1) Allow arbitrary function calls from one BPF function to another BPF function. As of today when writing BPF programs, __always_inline had to be used in the BPF C programs for all