Re: [PATCH bpf-next v2 0/2] Transfer RCU lock state across subprog calls

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

 



Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:

On Mon,  5 Feb 2024 05:56:44 +0000 you wrote:
> David suggested during the discussion in [0] that we should handle RCU
> locks in a similar fashion to spin locks where the verifier understands
> when a lock held in a caller is released in callee, or lock taken in
> callee is released in a caller, or the callee is called within a lock
> critical section. This set extends the same semantics to RCU read locks
> and adds a few selftests to verify correct behavior. This issue has also
> come up for sched-ext programs.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Transfer RCU lock state between subprog calls
    https://git.kernel.org/bpf/bpf-next/c/6fceea0fa59f
  - [bpf-next,v2,2/2] selftests/bpf: Add tests for RCU lock transfer between subprogs
    https://git.kernel.org/bpf/bpf-next/c/8be6a0147af3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html






[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