[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eefe4853-8963-b165-7771-79a86cc3b831@fb.com>
Date: Fri, 31 Mar 2017 22:46:36 -0700
From: Alexei Starovoitov <ast@...com>
To: "Wangnan (F)" <wangnan0@...wei.com>,
"David S . Miller" <davem@...emloft.net>
CC: Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>, <netdev@...r.kernel.org>,
<kernel-team@...com>
Subject: Re: [PATCH v2 net-next 3/6] tools/lib/bpf: expose
bpf_program__set_type()
On 3/31/17 10:32 PM, Wangnan (F) wrote:
>
> OK. Then let your patch be merged first then let me do the code cleanup.
Thanks!
Once these two lib/bpf patches applied to net-next we can apply
the same to tip and there will be no conflicts during the merge
window.
I'm also planning to fix few things later:
- there is an obscure error
libbpf: relocation failed: no 11 section
It's printed when llvm generates access to global variables.
I think we need to improve the error message to point out the actual
reason of the failure, so the user can fix the program.
- there is another equally obscure error
libbpf: Program 'foo' contains non-map related relo data pointing to
section 8
It's happening when program is compiled with -g.
It's just a bug in libbpf and the fix is straightforward.
so I suspect these fixes will also go into both net-next and tip.
Powered by blists - more mailing lists