From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] bpf: Only fails the busy counter check in bpf_cgrp_storage_get if it creates storage
Date: Wed, 19 Mar 2025 02:10:34 +0000 [thread overview]
Message-ID: <174235023475.536550.5782919972344813926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250318182759.3676094-1-martin.lau@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 18 Mar 2025 11:27:59 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> The current cgrp storage has a percpu counter, bpf_cgrp_storage_busy,
> to detect potential deadlock at a spin_lock that the local storage
> acquires during new storage creation.
>
> There are false positives. It turns out to be too noisy in
> production. For example, a bpf prog may be doing a
> bpf_cgrp_storage_get on map_a. An IRQ comes in and triggers
> another bpf_cgrp_storage_get on a different map_b. It will then
> trigger the false positive deadlock check in the percpu counter.
> On top of that, both are doing lookup only and no need to create
> new storage, so practically it does not need to acquire
> the spin_lock.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Only fails the busy counter check in bpf_cgrp_storage_get if it creates storage
https://git.kernel.org/bpf/bpf-next/c/f4edc66e48a6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-19 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 18:27 [PATCH bpf-next] bpf: Only fails the busy counter check in bpf_cgrp_storage_get if it creates storage Martin KaFai Lau
2025-03-19 2:10 ` 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=174235023475.536550.5782919972344813926.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=kernel-team@meta.com \
--cc=martin.lau@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