linux-kernel - Re: [PATCH bpf-next] bpf: Don't use rcu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 07 Dec 2022 00:50:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     David Vernet <void@...ifault.com>
Cc:     bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
        andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
        yhs@...a.com, john.fastabend@...il.com, kpsingh@...nel.org,
        sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
        linux-kernel@...r.kernel.org, kernel-team@...a.com,
        matus.jokay@...ba.sk
Subject: Re: [PATCH bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.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