netdev - Re: [PATCH bpf-next v2 00/16] bpf: Reduce the use of migrate

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]

Message-Id: 
 <173638923326.842935.15837805191875975956.git-patchwork-notify@kernel.org>
Date: Thu, 09 Jan 2025 02:20:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Hou Tao <houtao@...weicloud.com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org, martin.lau@...ux.dev,
 alexei.starovoitov@...il.com, andrii@...nel.org, eddyz87@...il.com,
 song@...nel.org, haoluo@...gle.com, yonghong.song@...ux.dev,
 daniel@...earbox.net, kpsingh@...nel.org, sdf@...ichev.me, jolsa@...nel.org,
 john.fastabend@...il.com, houtao1@...wei.com, xukuohai@...wei.com
Subject: Re: [PATCH bpf-next v2 00/16] bpf: Reduce the use of
 migrate_{disable|enable}()

Hello:

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

On Wed,  8 Jan 2025 09:07:12 +0800 you wrote:
> From: Hou Tao <houtao1@...wei.com>
> 
> Hi,
> 
> The use of migrate_{disable|enable} pair in BPF is mainly due to the
> introduction of bpf memory allocator and the use of per-CPU data struct
> in its internal implementation. The caller needs to disable migration
> before invoking the alloc or free APIs of bpf memory allocator, and
> enable migration after the invocation.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,01/16] bpf: Remove migrate_{disable|enable} from LPM trie
    https://git.kernel.org/bpf/bpf-next/c/1b1a01db17af
  - [bpf-next,v2,02/16] bpf: Remove migrate_{disable|enable} in ->map_for_each_callback
    https://git.kernel.org/bpf/bpf-next/c/ea5b229630a6
  - [bpf-next,v2,03/16] bpf: Remove migrate_{disable|enable} in htab_elem_free
    https://git.kernel.org/bpf/bpf-next/c/53f2ba0b1cc0
  - [bpf-next,v2,04/16] bpf: Remove migrate_{disable|enable} from bpf_cgrp_storage_lock helpers
    https://git.kernel.org/bpf/bpf-next/c/25dc65f75b08
  - [bpf-next,v2,05/16] bpf: Remove migrate_{disable|enable} from bpf_task_storage_lock helpers
    https://git.kernel.org/bpf/bpf-next/c/9e6c958b5466
  - [bpf-next,v2,06/16] bpf: Disable migration when destroying inode storage
    https://git.kernel.org/bpf/bpf-next/c/e319cdc89566
  - [bpf-next,v2,07/16] bpf: Disable migration when destroying sock storage
    https://git.kernel.org/bpf/bpf-next/c/7d1032d1e303
  - [bpf-next,v2,08/16] bpf: Disable migration when cloning sock storage
    https://git.kernel.org/bpf/bpf-next/c/dfccfc47bde5
  - [bpf-next,v2,09/16] bpf: Disable migration in bpf_selem_free_rcu
    https://git.kernel.org/bpf/bpf-next/c/090d7f2e640b
  - [bpf-next,v2,10/16] bpf: Disable migration before calling ops->map_free()
    https://git.kernel.org/bpf/bpf-next/c/4b7e7cd1c105
  - [bpf-next,v2,11/16] bpf: Remove migrate_{disable|enable} in bpf_obj_free_fields()
    https://git.kernel.org/bpf/bpf-next/c/1d2dbe7120e8
  - [bpf-next,v2,12/16] bpf: Remove migrate_{disable,enable} in bpf_cpumask_release()
    https://git.kernel.org/bpf/bpf-next/c/6a52b965ab6f
  - [bpf-next,v2,13/16] bpf: Remove migrate_{disable|enable} from bpf_selem_alloc()
    https://git.kernel.org/bpf/bpf-next/c/2269b32ab00e
  - [bpf-next,v2,14/16] bpf: Remove migrate_{disable|enable} from bpf_local_storage_alloc()
    https://git.kernel.org/bpf/bpf-next/c/4855a75ebf48
  - [bpf-next,v2,15/16] bpf: Remove migrate_{disable|enable} from bpf_local_storage_free()
    https://git.kernel.org/bpf/bpf-next/c/7b984359e097
  - [bpf-next,v2,16/16] bpf: Remove migrate_{disable|enable} from bpf_selem_free()
    https://git.kernel.org/bpf/bpf-next/c/d86088e2c35d

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