lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0206fefe-ccbd-1e7c-6bb5-51254e416d84@iogearbox.net>
Date:   Wed, 17 Jan 2018 00:15:16 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Wei Yongjun <weiyongjun1@...wei.com>,
        Alexei Starovoitov <ast@...nel.org>
Cc:     netdev@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH -next] bpf: cpumap: make some functions static

On 01/16/2018 12:27 PM, Wei Yongjun wrote:
> Fixes the following sparse warnings:
> 
> kernel/bpf/cpumap.c:146:6: warning:
>  symbol '__cpu_map_queue_destructor' was not declared. Should it be static?
> kernel/bpf/cpumap.c:225:16: warning:
>  symbol 'cpu_map_build_skb' was not declared. Should it be static?
> kernel/bpf/cpumap.c:340:26: warning:
>  symbol '__cpu_map_entry_alloc' was not declared. Should it be static?
> kernel/bpf/cpumap.c:398:6: warning:
>  symbol '__cpu_map_entry_free' was not declared. Should it be static?
> kernel/bpf/cpumap.c:441:6: warning:
>  symbol '__cpu_map_entry_replace' was not declared. Should it be static?
> kernel/bpf/cpumap.c:454:5: warning:
>  symbol 'cpu_map_delete_elem' was not declared. Should it be static?
> kernel/bpf/cpumap.c:467:5: warning:
>  symbol 'cpu_map_update_elem' was not declared. Should it be static?
> kernel/bpf/cpumap.c:505:6: warning:
>  symbol 'cpu_map_free' was not declared. Should it be static?
> 
> Signed-off-by: Wei Yongjun <weiyongjun1@...wei.com>

Applied to bpf-next, thanks Wei!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ