[PATCH v4] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap
马尔斯
mars14850 at gmail.com
Tue Mar 14 03:21:40 CET 2023
Ok, that was my mistake. I’ll send the new patch later :)
Sent from my iPhone
> On Mar 14, 2023, at 01:22, Stephen Hemminger <stephen at networkplumber.org> wrote:
>
> On Mon, 13 Mar 2023 17:07:29 +0000
> Konstantin Ananyev <konstantin.ananyev at huawei.com> wrote:
>
>>> I've read the libbpf code again and I found some other functions with
>>> pure 'bpf_' prefix. Should we rename all the functions whose names
>>> start with pure 'bpf_'?
>>
>> I thought you already prefixed all non-static functions in the lib...
>> Or do I miss something?
>
> Right, it was bpf_validate, bpf_jit_XXX that were not prefixed.
>
> .../build/lib/librte_bpf.a.p $ nm * | grep ' T ' | grep -v 'rte_bpf'
> 0000000000000070 T bpf_jit
> 0000000000003210 T bpf_jit_x86
> 00000000000021f0 T bpf_validate
More information about the dev
mailing list