From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf 0/3] bpf: Fix objects stuck in free_by_rcu_ttrace
Date: Thu, 01 Oct 2026 16:50:31 +0000 [thread overview]
Message-ID: <179087343109.3011010.17144166539288469552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930095920.601738-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 30 Sep 2026 09:59:17 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> The objects that bpf_mem_alloc frees while RCU tasks trace GP is in flight
> stay in free_by_rcu_ttrace list until the same bpf_mem_cache frees or
> allocates in bulk again.
>
> Patch 1 - refactoring. No functional change.
> Patch 2 - the fix.
> Patch 3 - selftest.
>
> [...]
Here is the summary with links:
- [bpf,1/3] bpf: Factor out __do_call_rcu_ttrace()
https://git.kernel.org/bpf/bpf/c/47f4f695cec1
- [bpf,2/3] bpf: Fix objects stuck in free_by_rcu_ttrace
https://git.kernel.org/bpf/bpf/c/fbd97dd1d3ce
- [bpf,3/3] selftests/bpf: Add a test for objects stuck in free_by_rcu_ttrace
https://git.kernel.org/bpf/bpf/c/aeb709c767ae
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-10-01 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:59 [PATCH bpf 0/3] bpf: Fix objects stuck in free_by_rcu_ttrace Alexei Starovoitov
2026-09-30 9:59 ` [PATCH bpf 1/3] bpf: Factor out __do_call_rcu_ttrace() Alexei Starovoitov
2026-09-30 9:59 ` [PATCH bpf 2/3] bpf: Fix objects stuck in free_by_rcu_ttrace Alexei Starovoitov
2026-09-30 9:59 ` [PATCH bpf 3/3] selftests/bpf: Add a test for " Alexei Starovoitov
2026-10-01 16: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=179087343109.3011010.17144166539288469552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--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