From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <hffilwlqm@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, maciej.fijalkowski@intel.com,
eddyz87@gmail.com, puranjay@kernel.org, jakub@cloudflare.com,
pulehui@huawei.com, kernel-patches-bot@fb.com
Subject: Re: [PATCH v6 bpf-next 0/3] bpf: Fix tailcall hierarchy
Date: Sat, 20 Jul 2024 03:00:31 +0000 [thread overview]
Message-ID: <172144443181.23894.1730433899460486996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240714123902.32305-1-hffilwlqm@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 14 Jul 2024 20:38:59 +0800 you wrote:
> This patchset fixes a tailcall hierarchy issue.
>
> The issue is confirmed in the discussions of "bpf, x64: Fix tailcall
> infinite loop"[0].
>
> The issue has been resolved on both x86_64 and arm64[1].
>
> [...]
Here is the summary with links:
- [v6,bpf-next,1/3] bpf, x64: Fix tailcall hierarchy
https://git.kernel.org/bpf/bpf-next/c/00ac9693a3ba
- [v6,bpf-next,2/3] bpf, arm64: Fix tailcall hierarchy
https://git.kernel.org/bpf/bpf-next/c/a53c0f324aed
- [v6,bpf-next,3/3] selftests/bpf: Add testcases for tailcall hierarchy fixing
https://git.kernel.org/bpf/bpf-next/c/92a227f61911
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:[~2024-07-20 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 12:38 [PATCH v6 bpf-next 0/3] bpf: Fix tailcall hierarchy Leon Hwang
2024-07-14 12:39 ` [PATCH v6 bpf-next 1/3] bpf, x64: " Leon Hwang
2024-07-14 12:39 ` [PATCH v6 bpf-next 2/3] bpf, arm64: " Leon Hwang
2024-07-14 12:39 ` [PATCH v6 bpf-next 3/3] selftests/bpf: Add testcases for tailcall hierarchy fixing Leon Hwang
2024-07-19 23:52 ` [PATCH v6 bpf-next 0/3] bpf: Fix tailcall hierarchy bot+bpf-ci
2024-07-20 2:57 ` Alexei Starovoitov
2024-07-20 3:00 ` 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=172144443181.23894.1730433899460486996.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=hffilwlqm@gmail.com \
--cc=jakub@cloudflare.com \
--cc=kernel-patches-bot@fb.com \
--cc=maciej.fijalkowski@intel.com \
--cc=pulehui@huawei.com \
--cc=puranjay@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox