From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
eddyz87@gmail.com, bjorn@kernel.org, daniel@iogearbox.net,
ast@kernel.org, andrii@kernel.org, memxor@gmail.com,
yonghong.song@linux.dev, martin.lau@linux.dev, song@kernel.org,
jolsa@kernel.org, emil@etsalapatis.com, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v3 0/3] Fixes for tailcall with subprog and callback
Date: Fri, 17 Jul 2026 00:50:11 +0000 [thread overview]
Message-ID: <178424941139.1475787.18080893330670192934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260716120157.835937-1-pulehui@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Thu, 16 Jul 2026 12:01:54 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> This series fix two issues related to tailcall:
>
> patch 1: Fix tail_call_reachable state leak across call branches.
> patch 2: Reject callback subprogs invoke tailcall.
> patch 3: testcases for patch 1 and 2.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/3] bpf: Sync tail_call_reachable with callee state on entry
https://git.kernel.org/bpf/bpf-next/c/3513ea9dab6c
- [bpf-next,v3,2/3] bpf: Reject callback subprogs invoke tailcall
https://git.kernel.org/bpf/bpf-next/c/a41d0c30d764
- [bpf-next,v3,3/3] selftests/bpf: Add testcases for callback with tailcall
https://git.kernel.org/bpf/bpf-next/c/42bfd21a8b70
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-07-17 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 12:01 Pu Lehui
2026-07-16 12:01 ` [PATCH bpf-next v3 1/3] bpf: Sync tail_call_reachable with callee state on entry Pu Lehui
2026-07-16 12:01 ` [PATCH bpf-next v3 2/3] bpf: Reject callback subprogs invoke tailcall Pu Lehui
2026-07-16 12:01 ` [PATCH bpf-next v3 3/3] selftests/bpf: Add testcases for callback with tailcall Pu Lehui
2026-07-17 0: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=178424941139.1475787.18080893330670192934.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=song@kernel.org \
--cc=yonghong.song@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
Powered by JetHome