netdev - Re: [PATCH bpf-next 00/15] bpf: Introduce selectable memcg for bpf map

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <166015801536.14189.14692203185396182235.git-patchwork-notify@kernel.org>
Date:   Wed, 10 Aug 2022 19:00:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Yafang Shao <laoar.shao@...il.com>
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        kafai@...com, songliubraving@...com, yhs@...com,
        john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
        haoluo@...gle.com, jolsa@...nel.org, hannes@...xchg.org,
        mhocko@...nel.org, roman.gushchin@...ux.dev, shakeelb@...gle.com,
        songmuchun@...edance.com, akpm@...ux-foundation.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH bpf-next 00/15] bpf: Introduce selectable memcg for bpf map 

Hello:

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

On Wed, 10 Aug 2022 15:18:25 +0000 you wrote:
> On our production environment, we may load, run and pin bpf programs and
> maps in containers. For example, some of our networking bpf programs and
> maps are loaded and pinned by a process running in a container on our
> k8s environment. In this container, there're also running some other
> user applications which watch the networking configurations from remote
> servers and update them on this local host, log the error events, monitor
> the traffic, and do some other stuffs. Sometimes we may need to update
> these user applications to a new release, and in this update process we
> will destroy the old container and then start a new genration. In order not
> to interrupt the bpf programs in the update process, we will pin the bpf
> programs and maps in bpffs. That is the background and use case on our
> production environment.
> 
> [...]

Here is the summary with links:
  - [bpf-next,01/15] bpf: Remove unneeded memset in queue_stack_map creation
    https://git.kernel.org/bpf/bpf-next/c/083818156d1e
  - [bpf-next,02/15] bpf: Use bpf_map_area_free instread of kvfree
    https://git.kernel.org/bpf/bpf-next/c/8f58ee54c2ea
  - [bpf-next,03/15] bpf: Make __GFP_NOWARN consistent in bpf map creation
    https://git.kernel.org/bpf/bpf-next/c/992c9e13f593
  - [bpf-next,04/15] bpf: Use bpf_map_area_alloc consistently on bpf map creation
    https://git.kernel.org/bpf/bpf-next/c/73cf09a36bf7
  - [bpf-next,05/15] bpf: Fix incorrect mem_cgroup_put
    (no matching commit)
  - [bpf-next,06/15] bpf: Define bpf_map_{get,put}_memcg for !CONFIG_MEMCG_KMEM
    (no matching commit)
  - [bpf-next,07/15] bpf: Call bpf_map_init_from_attr() immediately after map creation
    (no matching commit)
  - [bpf-next,08/15] bpf: Save memcg in bpf_map_init_from_attr()
    (no matching commit)
  - [bpf-next,09/15] bpf: Use scoped-based charge in bpf_map_area_alloc
    (no matching commit)
  - [bpf-next,10/15] bpf: Introduce new helpers bpf_ringbuf_pages_{alloc,free}
    (no matching commit)
  - [bpf-next,11/15] bpf: Use bpf_map_kzalloc in arraymap
    (no matching commit)
  - [bpf-next,12/15] bpf: Use bpf_map_kvcalloc in bpf_local_storage
    (no matching commit)
  - [bpf-next,13/15] mm, memcg: Add new helper get_obj_cgroup_from_cgroup
    (no matching commit)
  - [bpf-next,14/15] bpf: Add return value for bpf_map_init_from_attr
    (no matching commit)
  - [bpf-next,15/15] bpf: Introduce selectable memcg for bpf map
    (no matching commit)

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