From: Leon Hwang <hffilwlqm@gmail.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
maciej.fijalkowski@intel.com, jakub@cloudflare.com,
iii@linux.ibm.com, hengqi.chen@gmail.com
Subject: Re: [RFC PATCH bpf-next v2 0/4] bpf, x64: Fix tailcall hierarchy
Date: Thu, 16 Nov 2023 16:33:26 +0800 [thread overview]
Message-ID: <5ee643a8-d39e-470b-83e9-9d550374e617@gmail.com> (raw)
In-Reply-To: <20231011152725.95895-1-hffilwlqm@gmail.com>
PING
On 11/10/23 23:27, Leon Hwang wrote:
> This patchset fixes a tailcall hierarchy issue with a better solution than v1[0].
>
> v1 solution stores tail_call_cnt on the stack of bpf prog:
>
> | STACK |
> +---------+ RBP
> | |
> | |
> | |
> +--| tcc_ptr |
> +->| tcc |
> | rbx |
> +---------+ RSP
>
> v2 solution stores tail_call_cnt on the stack of bpf prog's caller:
>
> | STACK |
> | |
> | rip |
> +->| tcc |
> | | rip |
> | | rbp |
> | +---------+ RBP
> | | |
> | | |
> | | |
> +--| tcc_ptr |
> | rbx |
> +---------+ RSP
>
> With this change, it requires less instructions to resolve this issue.
>
> For more resolving details, please read the following patches.
>
> The issue is confirmed in the discussions of "bpf, x64: Fix tailcall infinite
> loop"[1].
>
> Currently, I only resolve this issue on x86. The ones on arm64, s390x and
> loongarch are waiting to be resolved. So, the ci pipeline fails to run for this
> issue fixing.
>
> Hopefully, this issue on s390x and arm64 will be resolved soon.
>
> v1 -> v2:
> * address comments from Stanislav
> * Separate moving emit_nops() as first patch.
>
> Links:
> [0] https://lore.kernel.org/bpf/20231005145814.83122-1-hffilwlqm@gmail.com/
> [1] https://lore.kernel.org/bpf/6203dd01-789d-f02c-5293-def4c1b18aef@gmail.com/
>
> Leon Hwang (4):
> bpf, x64: Emit nops for X86_PATCH
> bpf, x64: Fix tailcall hierarchy
> bpf, x64: Load tail_call_cnt pointer
> selftests/bpf: Add testcases for tailcall hierarchy fixing
>
> arch/x86/net/bpf_jit_comp.c | 99 +++--
> .../selftests/bpf/prog_tests/tailcalls.c | 418 ++++++++++++++++++
> .../bpf/progs/tailcall_bpf2bpf_hierarchy1.c | 34 ++
> .../bpf/progs/tailcall_bpf2bpf_hierarchy2.c | 55 +++
> .../bpf/progs/tailcall_bpf2bpf_hierarchy3.c | 46 ++
> 5 files changed, 606 insertions(+), 46 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy1.c
> create mode 100644 tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy2.c
> create mode 100644 tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy3.c
>
>
> base-commit: 644b54d80d572438a815c05b1bab2b7871e1e5a1
next prev parent reply other threads:[~2023-11-16 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:27 [RFC PATCH bpf-next v2 0/4] bpf, x64: Fix tailcall hierarchy Leon Hwang
2023-10-11 15:27 ` [RFC PATCH bpf-next v2 1/4] bpf, x64: Emit nops for X86_PATCH Leon Hwang
2023-12-05 13:08 ` Maciej Fijalkowski
2023-10-11 15:27 ` [RFC PATCH bpf-next v2 2/4] bpf, x64: Fix tailcall hierarchy Leon Hwang
2023-12-05 23:03 ` Maciej Fijalkowski
2023-12-06 6:51 ` Leon Hwang
2023-12-11 18:02 ` Maciej Fijalkowski
2023-12-13 2:48 ` Leon Hwang
2023-12-21 12:02 ` Maciej Fijalkowski
2023-12-21 14:56 ` Leon Hwang
2024-01-04 6:23 ` Alexei Starovoitov
2023-10-11 15:27 ` [RFC PATCH bpf-next v2 3/4] bpf, x64: Load tail_call_cnt pointer Leon Hwang
2023-12-11 18:03 ` Maciej Fijalkowski
2023-12-13 2:49 ` Leon Hwang
2023-10-11 15:27 ` [RFC PATCH bpf-next v2 4/4] selftests/bpf: Add testcases for tailcall hierarchy fixing Leon Hwang
2023-12-11 18:05 ` Maciej Fijalkowski
2023-12-13 3:09 ` Leon Hwang
2023-11-16 8:33 ` Leon Hwang [this message]
2023-11-17 21:40 ` [RFC PATCH bpf-next v2 0/4] bpf, x64: Fix tailcall hierarchy Alexei Starovoitov
2023-11-20 12:41 ` Maciej Fijalkowski
2023-12-05 3:09 ` Alexei Starovoitov
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=5ee643a8-d39e-470b-83e9-9d550374e617@gmail.com \
--to=hffilwlqm@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hengqi.chen@gmail.com \
--cc=iii@linux.ibm.com \
--cc=jakub@cloudflare.com \
--cc=maciej.fijalkowski@intel.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