public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
	alexei.starovoitov@gmail.com, andrii@kernel.org,
	daniel@iogearbox.net, memxor@gmail.com, martin.lau@kernel.org,
	kpsingh@kernel.org, yonghong.song@linux.dev, song@kernel.org,
	haoluo@google.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v7 00/17] Remove task and cgroup local storage percpu counters
Date: Fri, 06 Feb 2026 23:00:28 +0000	[thread overview]
Message-ID: <177041882833.1106743.17316630593839442939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260205222916.1788211-1-ameryhung@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Thu,  5 Feb 2026 14:28:58 -0800 you wrote:
> * Motivation *
> 
> The goal of this patchset is to make bpf syscalls and helpers updating
> task and cgroup local storage more robust by removing percpu counters
> in them. Task local storage and cgroup storage each employs a percpu
> counter to prevent deadlock caused by recursion. Since the underlying
> bpf local storage takes spinlocks in various operations, bpf programs
> running recursively may try to take a spinlock which is already taken.
> For example, when a tracing bpf program called recursively during
> bpf_task_storage_get(..., F_CREATE) tries to call
> bpf_task_storage_get(..., F_CREATE) again, it will cause AA deadlock
> if the percpu variable is not in place.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,01/17] bpf: Select bpf_local_storage_map_bucket based on bpf_local_storage
    https://git.kernel.org/bpf/bpf-next/c/0ccef7079ea8
  - [bpf-next,v7,02/17] bpf: Convert bpf_selem_unlink_map to failable
    https://git.kernel.org/bpf/bpf-next/c/1b7e0cae85ac
  - [bpf-next,v7,03/17] bpf: Convert bpf_selem_link_map to failable
    https://git.kernel.org/bpf/bpf-next/c/fd103ffc57c9
  - [bpf-next,v7,04/17] bpf: Convert bpf_selem_unlink to failable
    https://git.kernel.org/bpf/bpf-next/c/403e935f9158
  - [bpf-next,v7,05/17] bpf: Change local_storage->lock and b->lock to rqspinlock
    https://git.kernel.org/bpf/bpf-next/c/8dabe34b9d5b
  - [bpf-next,v7,06/17] bpf: Remove task local storage percpu counter
    https://git.kernel.org/bpf/bpf-next/c/4a98c2efa613
  - [bpf-next,v7,07/17] bpf: Remove cgroup local storage percpu counter
    https://git.kernel.org/bpf/bpf-next/c/5254de7b9607
  - [bpf-next,v7,08/17] bpf: Remove unused percpu counter from bpf_local_storage_map_free
    https://git.kernel.org/bpf/bpf-next/c/3417dffb5833
  - [bpf-next,v7,09/17] bpf: Prepare for bpf_selem_unlink_nofail()
    https://git.kernel.org/bpf/bpf-next/c/c8be3da14718
  - [bpf-next,v7,10/17] bpf: Support lockless unlink when freeing map or local storage
    https://git.kernel.org/bpf/bpf-next/c/5d800f87d0a5
  - [bpf-next,v7,11/17] bpf: Switch to bpf_selem_unlink_nofail in bpf_local_storage_{map_free, destroy}
    https://git.kernel.org/bpf/bpf-next/c/0be08389c7f2
  - [bpf-next,v7,12/17] selftests/bpf: Update sk_storage_omem_uncharge test
    https://git.kernel.org/bpf/bpf-next/c/d652f425d5e3
  - [bpf-next,v7,13/17] selftests/bpf: Update task_local_storage/recursion test
    https://git.kernel.org/bpf/bpf-next/c/e4772031d105
  - [bpf-next,v7,14/17] selftests/bpf: Update task_local_storage/task_storage_nodeadlock test
    https://git.kernel.org/bpf/bpf-next/c/902a79b6389f
  - [bpf-next,v7,15/17] selftests/bpf: Remove test_task_storage_map_stress_lookup
    https://git.kernel.org/bpf/bpf-next/c/e02cf06b85f8
  - [bpf-next,v7,16/17] selftests/bpf: Choose another percpu variable in bpf for btf_dump test
    https://git.kernel.org/bpf/bpf-next/c/cdce7b0848f6
  - [bpf-next,v7,17/17] selftests/bpf: Fix outdated test on storage->smap
    https://git.kernel.org/bpf/bpf-next/c/97b859b5ed04

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



      parent reply	other threads:[~2026-02-06 23:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 22:28 [PATCH bpf-next v7 00/17] Remove task and cgroup local storage percpu counters Amery Hung
2026-02-05 22:28 ` [PATCH bpf-next v7 01/17] bpf: Select bpf_local_storage_map_bucket based on bpf_local_storage Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 02/17] bpf: Convert bpf_selem_unlink_map to failable Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 03/17] bpf: Convert bpf_selem_link_map " Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 04/17] bpf: Convert bpf_selem_unlink " Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 05/17] bpf: Change local_storage->lock and b->lock to rqspinlock Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 06/17] bpf: Remove task local storage percpu counter Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 07/17] bpf: Remove cgroup " Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 08/17] bpf: Remove unused percpu counter from bpf_local_storage_map_free Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 09/17] bpf: Prepare for bpf_selem_unlink_nofail() Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 10/17] bpf: Support lockless unlink when freeing map or local storage Amery Hung
2026-02-06 23:25   ` Martin KaFai Lau
2026-02-05 22:29 ` [PATCH bpf-next v7 11/17] bpf: Switch to bpf_selem_unlink_nofail in bpf_local_storage_{map_free, destroy} Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 12/17] selftests/bpf: Update sk_storage_omem_uncharge test Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 13/17] selftests/bpf: Update task_local_storage/recursion test Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 14/17] selftests/bpf: Update task_local_storage/task_storage_nodeadlock test Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 15/17] selftests/bpf: Remove test_task_storage_map_stress_lookup Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 16/17] selftests/bpf: Choose another percpu variable in bpf for btf_dump test Amery Hung
2026-02-05 22:29 ` [PATCH bpf-next v7 17/17] selftests/bpf: Fix outdated test on storage->smap Amery Hung
2026-02-06 23:00 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177041882833.1106743.17316630593839442939.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=kernel-team@meta.com \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox