Re: [PATCH bpf-next v1 2/7] bpf: Be consistent between {acquire,find,release}_lock_state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2024-11-20 at 16:53 -0800, Kumar Kartikeya Dwivedi wrote:
> Both acquire_lock_state and release_lock_state take the bpf_func_state
> as a parameter, while find_lock_state does not. Future patches will end
> up requiring operating on non-cur_func(env) bpf_func_state (for
> resilient locks), hence just make the prototype consistent and take
> bpf_func_state directly.
> 
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@xxxxxxxxx>
> ---

Acked-by: Eduard Zingerman <eddyz87@xxxxxxxxx>






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux