Re: [PATCH net-next 3/3] bpf: make jited programs visible in traces

2017-02-20 Thread Daniel Borkmann
On 02/20/2017 08:07 PM, Daniel Borkmann wrote: On 02/20/2017 08:05 PM, Eric Dumazet wrote: [...] Latest net-next tree dies on my hosts, and my bisection came to this commit. Thanks for the report, I'll take a look! Fyi, fix will come tomorrow.

Re: [PATCH net-next 3/3] bpf: make jited programs visible in traces

2017-02-20 Thread Daniel Borkmann
On 02/20/2017 08:05 PM, Eric Dumazet wrote: [...] Latest net-next tree dies on my hosts, and my bisection came to this commit. Thanks for the report, I'll take a look!

Re: [PATCH net-next 3/3] bpf: make jited programs visible in traces

2017-02-20 Thread Eric Dumazet
On Thu, 2017-02-16 at 22:24 +0100, Daniel Borkmann wrote: > Long standing issue with JITed programs is that stack traces from > function tracing check whether a given address is kernel code > through {__,}kernel_text_address(), which checks for code in core > kernel, modules and dynamically allocat

[PATCH net-next 3/3] bpf: make jited programs visible in traces

2017-02-16 Thread Daniel Borkmann
Long standing issue with JITed programs is that stack traces from function tracing check whether a given address is kernel code through {__,}kernel_text_address(), which checks for code in core kernel, modules and dynamically allocated ftrace trampolines. But what is still missing is BPF JITed prog