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, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf v1 1/1] bpf: Dissociate struct_ops program with map if map_update fails
Date: Fri, 17 Apr 2026 19:10:08 +0000 [thread overview]
Message-ID: <177645300829.123271.1060726016212544246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260417174900.2895486-1-ameryhung@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 17 Apr 2026 10:49:00 -0700 you wrote:
> Currently, when bpf_struct_ops_map_update_elem() fails, the programs'
> st_ops_assoc will remain set. They may become dangling pointers if the
> map is freed later, but they will never be dereferenced since the
> struct_ops attachment did not succeed. However, if one of the programs
> is subsequently attached as part of another struct_ops map, its
> st_ops_assoc will be poisoned even though its old st_ops_assoc was stale
> from a failed attachment.
>
> [...]
Here is the summary with links:
- [bpf,v1,1/1] bpf: Dissociate struct_ops program with map if map_update fails
https://git.kernel.org/bpf/bpf/c/f75aeb2de891
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-04-17 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 17:49 [PATCH bpf v1 1/1] bpf: Dissociate struct_ops program with map if map_update fails Amery Hung
2026-04-17 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=177645300829.123271.1060726016212544246.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=eddyz87@gmail.com \
--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