BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@kernel.org,
	yonghong.song@linux.dev, laoar.shao@gmail.com,
	void@manifault.com, tj@kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] Transfer RCU lock state across subprog calls
Date: Tue, 06 Feb 2024 04:10:26 +0000	[thread overview]
Message-ID: <170719262630.31872.2248639771567354367.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240205055646.1112186-1-memxor@gmail.com>

Hello:

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

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



      parent reply	other threads:[~2024-02-06  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  5:56 [PATCH bpf-next v2 0/2] Transfer RCU lock state across subprog calls Kumar Kartikeya Dwivedi
2024-02-05  5:56 ` [PATCH bpf-next v2 1/2] bpf: Transfer RCU lock state between " Kumar Kartikeya Dwivedi
2024-02-05 15:14   ` David Vernet
2024-02-05  5:56 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add tests for RCU lock transfer between subprogs Kumar Kartikeya Dwivedi
2024-02-05 12:55   ` Yafang Shao
2024-02-05 15:14   ` David Vernet
2024-02-06  4:10 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=170719262630.31872.2248639771567354367.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=tj@kernel.org \
    --cc=void@manifault.com \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox