Re: [PATCH bpf-next v2 0/3] bpf: Handle MEM_RCU type properly - patchwork-bot+netdevbpf

From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] bpf: Handle MEM_RCU type properly
Date: Sun, 04 Dec 2022 21:00:15 +0000	[thread overview]
Message-ID: <167018761545.21113.14652815039544773708.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221203184557.476871-1-yhs@fb.com>

Hello:

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

On Sat, 3 Dec 2022 10:45:57 -0800 you wrote:
> Patch set [1] added rcu support for bpf programs. In [1], a rcu
> pointer is considered to be trusted and not null. This is actually
> not true in some cases. The rcu pointer could be null, and for non-null
> rcu pointer, it may have reference count of 0. This small patch set
> fixed this problem. Patch 1 is the kernel fix. Patch 2 adjusted
> selftests properly. Patch 3 added documentation for newly-introduced
> KF_RCU flag.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/3] bpf: Handle MEM_RCU type properly
    https://git.kernel.org/bpf/bpf-next/c/fca1aa75518c
  - [bpf-next,v2,2/3] selftests/bpf: Fix rcu_read_lock test with new MEM_RCU semantics
    https://git.kernel.org/bpf/bpf-next/c/8723ec22a31d
  - [bpf-next,v2,3/3] docs/bpf: Add KF_RCU documentation
    https://git.kernel.org/bpf/bpf-next/c/f53625649888

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