Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167037421590.21168.15544394333663900920.git-patchwork-notify@kernel.org>
Date:   Wed, 07 Dec 2022 00:50:15 +0000
References: <20221206210538.597606-1-void@manifault.com>
In-Reply-To: <20221206210538.597606-1-void@manifault.com>
To:     David Vernet <void@manifault.com>
Cc:     bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
        yhs@meta.com, john.fastabend@gmail.com, kpsingh@kernel.org,
        sdf@google.com, haoluo@google.com, jolsa@kernel.org,
        linux-kernel@vger.kernel.org, kernel-team@meta.com,
        matus.jokay@stuba.sk
Precedence: bulk

Hello:

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

On Tue,  6 Dec 2022 15:05:38 -0600 you wrote:
> A series of prior patches added some kfuncs that allow struct
> task_struct * objects to be used as kptrs. These kfuncs leveraged the
> 'refcount_t rcu_users' field of the task for performing refcounting.
> This field was used instead of 'refcount_t usage', as we wanted to
> leverage the safety provided by RCU for ensuring a task's lifetime.
> 
> A struct task_struct is refcounted by two different refcount_t fields:
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs
    https://git.kernel.org/bpf/bpf-next/c/156ed20d22ee

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