From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
kuni1840@gmail.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
eulgyukim@snu.ac.kr
Subject: Re: [PATCH v2 bpf] bpf: Free reuseport cBPF prog after RCU grace period.
Date: Fri, 08 May 2026 20:50:06 +0000 [thread overview]
Message-ID: <177827340608.844515.12414699446325110304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260426012647.3233119-1-kuniyu@google.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 26 Apr 2026 01:26:43 +0000 you wrote:
> Eulgyu Kim reported the splat below with a repro. [0]
>
> The repro sets up a UDP reuseport group with a cBPF prog and
> replaces it with a new one while another thread is sending
> a UDP packet to the group.
>
> The reuseport prog is freed by sk_reuseport_prog_free().
> bpf_prog_put() is called for "e"BPF prog to destruct through
> multiple stages while cBPF prog is freed immediately by
> bpf_release_orig_filter() and bpf_prog_free().
>
> [...]
Here is the summary with links:
- [v2,bpf] bpf: Free reuseport cBPF prog after RCU grace period.
https://git.kernel.org/bpf/bpf/c/18fc650ccd7f
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-05-08 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 1:26 [PATCH v2 bpf] bpf: Free reuseport cBPF prog after RCU grace period Kuniyuki Iwashima
2026-05-08 20:42 ` Martin KaFai Lau
2026-05-08 22:13 ` Kuniyuki Iwashima
2026-05-08 20:50 ` 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=177827340608.844515.12414699446325110304.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=eulgyukim@snu.ac.kr \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.