From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 1/1] bpf: Do not allow deleting local storage in NMI
Date: Thu, 19 Mar 2026 19:10:06 +0000 [thread overview]
Message-ID: <177394740604.1768581.14896493417337361938.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260319025716.2361065-1-ameryhung@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 18 Mar 2026 19:57:16 -0700 you wrote:
> Currently, local storage may deadlock when deferring freeing selem or
> local storage through kfree_rcu(), call_rcu() or call_rcu_tasks_trace()
> in NMI or reentrant. Since deleting selem in NMI is an unlikely use
> case, partially mitigate it by returning error when calling from
> bpf_xxx_storage_delete() helpers in NMI. Note that, it is still possible
> to deadlock through reentrant. A full mitigation requires returning
> error when irqs_disabled() is true, which, however is too heavy-handed
> for bpf_xxx_storage_delete().
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/1] bpf: Do not allow deleting local storage in NMI
https://git.kernel.org/bpf/bpf-next/c/350de5b8a9be
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:[~2026-03-19 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 2:57 [PATCH bpf-next v2 1/1] bpf: Do not allow deleting local storage in NMI Amery Hung
2026-03-19 19: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=177394740604.1768581.14896493417337361938.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
/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