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 from the initial pass is n
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 pass nor freed.
Good c
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.
>
> But this is really
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 you relocate the call
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 updates for your *net-next* tree.
>> >
>> > The main
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 calls from one BPF func
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 writing BPF programs, _
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 fun
