Re: [PATCH bpf-next 1/5] bpf: introduce BPF_PROG_TYPE_USER

Hi Song, I love your patch! Perhaps something to improve: [auto build test WARNING on bpf-next/master] url: https://github.com/0day-ci/linux/commits/Song-Liu/introduce-BPF_PROG_TYPE_USER/20200801-165208 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master config:

Re: [PATCH bpf-next 1/5] bpf: introduce BPF_PROG_TYPE_USER

Hi Song, I love your patch! Yet something to improve: [auto build test ERROR on bpf-next/master] url: https://github.com/0day-ci/linux/commits/Song-Liu/introduce-BPF_PROG_TYPE_USER/20200801-165208 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master config:

Re: [PATCH bpf-next 1/5] bpf: introduce BPF_PROG_TYPE_USER

Hi Song, I love your patch! Yet something to improve: [auto build test ERROR on bpf-next/master] url: https://github.com/0day-ci/linux/commits/Song-Liu/introduce-BPF_PROG_TYPE_USER/20200801-165208 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master config:

[PATCH bpf-next 1/5] bpf: introduce BPF_PROG_TYPE_USER

As of today, to trigger BPF program from user space, the common practise is to create a uprobe on a special function and calls that function. For example, bpftrace uses BEGIN_trigger and END_trigger for the BEGIN and END programs. However, uprobe is not ideal for this use case. First, uprobe uses