On 08/09/2017 11:26 PM, David Miller wrote:
From: Daniel Borkmann
Date: Wed, 09 Aug 2017 22:32:34 +0200
For the case of cilium, we are not in control of the kernel, by
the way, we run a few probes that are small BPF insns snippets
that test the kernel for presence of
From: Daniel Borkmann
Date: Wed, 09 Aug 2017 22:32:34 +0200
> For the case of cilium, we are not in control of the kernel, by
> the way, we run a few probes that are small BPF insns snippets
> that test the kernel for presence of certain features (e.g. helper,
> verifier,
On 08/09/2017 08:01 PM, David Miller wrote:
From: Daniel Borkmann
Date: Wed, 09 Aug 2017 19:00:58 +0200
On 08/09/2017 06:55 PM, David Miller wrote:
From: Daniel Borkmann
Date: Wed, 9 Aug 2017 12:23:53 +0200
[1]
From: Daniel Borkmann
Date: Wed, 09 Aug 2017 19:00:58 +0200
> On 08/09/2017 06:55 PM, David Miller wrote:
>> From: Daniel Borkmann
>> Date: Wed, 9 Aug 2017 12:23:53 +0200
>>
>>>[1] https://github.com/borkmann/llvm/tree/bpf-insns
>>
>> How is this
On 08/09/2017 07:00 PM, Daniel Borkmann wrote:
On 08/09/2017 06:55 PM, David Miller wrote:
From: Daniel Borkmann
Date: Wed, 9 Aug 2017 12:23:53 +0200
[1] https://github.com/borkmann/llvm/tree/bpf-insns
How is this "backwards compatible"?
If someone takes a new
On 08/09/2017 06:55 PM, David Miller wrote:
From: Daniel Borkmann
Date: Wed, 9 Aug 2017 12:23:53 +0200
[1] https://github.com/borkmann/llvm/tree/bpf-insns
How is this "backwards compatible"?
If someone takes a new LLVM and tries to load those programs
into an
From: Daniel Borkmann
Date: Wed, 9 Aug 2017 12:23:53 +0200
> [1] https://github.com/borkmann/llvm/tree/bpf-insns
How is this "backwards compatible"?
If someone takes a new LLVM and tries to load those programs
into an older kernel they will be rejected.
There appears