BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	mykyta.yatsenko5@gmail.com
Subject: Re: [PATCH bpf-next v2] bpf: Drop percpu_counter from the htab element count
Date: Fri, 30 Oct 2026 22:20:09 +0000	[thread overview]
Message-ID: <179339880981.1802147.12535140173060798885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021185117.650403-1-puranjay@kernel.org>

Hello:

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

On Wed, 21 Oct 2026 11:51:16 -0700 you wrote:
> The element count of a large non-preallocated hash map is a
> percpu_counter, whose slow path takes fbc->lock with
> raw_spin_lock_irqsave(). That is not safe against BPF programs that run
> while the lock is held or contended: NMI programs and, as
> queued_spin_lock_slowpath() calls trace_contention_end() with the lock
> already held, programs attached to the contention_end tracepoint. If such
> a program updates the same map it spins on the lock its own CPU holds:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Drop percpu_counter from the htab element count
    https://git.kernel.org/bpf/bpf/c/1cd28b5354ab

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-10-30 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 18:51 [PATCH bpf-next v2] bpf: Drop percpu_counter from the htab element count Puranjay Mohan
2026-10-21 19:23 ` bot+bpf-ci
2026-10-22 10:00   ` Puranjay Mohan
2026-10-30 22:20 ` 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=179339880981.1802147.12535140173060798885.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=puranjay@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