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, song@kernel.org,
iii@linux.ibm.com, xukuohai@huawei.com,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next 0/3] bpf, x64: Fix tailcall infinite loop
Date: Tue, 12 Sep 2023 20:20:26 +0000 [thread overview]
Message-ID: <169455002685.29579.6381172628752155950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912150442.2009-1-hffilwlqm@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 12 Sep 2023 23:04:39 +0800 you wrote:
> This patch series fixes a tailcall infinite loop on x64.
>
> From commit ebf7d1f508a73871 ("bpf, x64: rework pro/epilogue and tailcall
> handling in JIT"), the tailcall on x64 works better than before.
>
> From commit e411901c0b775a3a ("bpf: allow for tailcalls in BPF subprograms
> for x64 JIT"), tailcall is able to run in BPF subprograms on x64.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf, x64: Comment tail_call_cnt initialisation
https://git.kernel.org/bpf/bpf-next/c/2bee9770f3c6
- [bpf-next,2/3] bpf, x64: Fix tailcall infinite loop
https://git.kernel.org/bpf/bpf-next/c/2b5dcb31a19a
- [bpf-next,3/3] selftests/bpf: Add testcases for tailcall infinite loop fixing
https://git.kernel.org/bpf/bpf-next/c/e13b5f2f3ba3
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:[~2023-09-12 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 15:04 [PATCH bpf-next 0/3] bpf, x64: Fix tailcall infinite loop Leon Hwang
2023-09-12 15:04 ` [PATCH bpf-next 1/3] bpf, x64: Comment tail_call_cnt initialisation Leon Hwang
2023-09-12 15:04 ` [PATCH bpf-next 2/3] bpf, x64: Fix tailcall infinite loop Leon Hwang
2023-09-12 15:04 ` [PATCH bpf-next 3/3] selftests/bpf: Add testcases for tailcall infinite loop fixing Leon Hwang
2023-09-12 20:20 ` 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=169455002685.29579.6381172628752155950.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=hffilwlqm@gmail.com \
--cc=iii@linux.ibm.com \
--cc=kernel-patches-bot@fb.com \
--cc=maciej.fijalkowski@intel.com \
--cc=song@kernel.org \
--cc=xukuohai@huawei.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