Re: [PATCH bpf-next v2 1/4] bpf: export bpf_map_inc_not_zero

2019-08-11 Thread Yonghong Song
On 8/9/19 9:10 AM, Stanislav Fomichev wrote: > Rename existing bpf_map_inc_not_zero to __bpf_map_inc_not_zero to > indicate that it's caller's responsibility to do proper locking. > Create and export bpf_map_inc_not_zero wrapper that properly > locks map_idr_lock. Will be used in the next commit

[PATCH bpf-next v2 1/4] bpf: export bpf_map_inc_not_zero

2019-08-09 Thread Stanislav Fomichev
Rename existing bpf_map_inc_not_zero to __bpf_map_inc_not_zero to indicate that it's caller's responsibility to do proper locking. Create and export bpf_map_inc_not_zero wrapper that properly locks map_idr_lock. Will be used in the next commit to hold a map while cloning a socket. Cc: Martin KaFai