From: "Björn Töpel" <bjorn@kernel.org>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Pu Lehui <pulehui@huaweicloud.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
bot+bpf-ci@kernel.org, bpf@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, puranjay@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
pulehui@huawei.com, martin.lau@kernel.org, clm@meta.com,
ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v6 6/7] riscv, bpf: Mixing bpf2bpf and tailcalls
Date: Tue, 21 Jul 2026 20:12:59 +0200 [thread overview]
Message-ID: <87mrvkus7o.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <DK3GTYQ5UOMO.CVL471XPD0AT@gmail.com>
Folks,
Sorry for the delay. This slipped between netdevconf and ongoing PTO!
"Kumar Kartikeya Dwivedi" <memxor@gmail.com> writes:
> On Fri Jul 17, 2026 at 9:37 AM CEST, Pu Lehui wrote:
>> Just a quick note that the verifier fix we discussed has now landed in
>> bpf-next [0]. Looking forward to your feedback on v6 whenever you get a
>> chance. :)
Nice one! Happy to see that!
> Yep, if there are no more concerns, it would make sense to pull this in.
>
> Björn, what do you think?
That was the only concern I had!
For the whole series:
Reviewed-by: Björn Töpel <bjorn@kernel.org>
Acked-by: Björn Töpel <bjorn@kernel.org>
next prev parent reply other threads:[~2026-07-21 18:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 6:44 [PATCH bpf-next v6 0/7] Mixing bpf2bpf and tailcalls for RV64 Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 1/7] bpf: Extract the is_struct_ops_tramp helper Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 2/7] riscv, bpf: Fix memory leak in bpf_jit_free Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 3/7] riscv, bpf: Using kvzalloc_objs to allocate cache buffer Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 4/7] riscv, bpf: Fix kernel stack corruption in tailcall with CFI Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 5/7] riscv, bpf: Add RV_TAILCALL_OFFSET macro to format tailcall offset Pu Lehui
2026-07-08 6:44 ` [PATCH bpf-next v6 6/7] riscv, bpf: Mixing bpf2bpf and tailcalls Pu Lehui
2026-07-08 7:35 ` bot+bpf-ci
2026-07-08 8:54 ` Pu Lehui
2026-07-09 11:37 ` Björn Töpel
2026-07-09 15:09 ` Pu Lehui
2026-07-09 19:51 ` Björn Töpel
2026-07-10 0:53 ` Pu Lehui
2026-07-10 9:43 ` Daniel Borkmann
2026-07-17 7:37 ` Pu Lehui
2026-07-20 14:24 ` Kumar Kartikeya Dwivedi
2026-07-21 18:12 ` Björn Töpel [this message]
2026-07-08 6:44 ` [PATCH bpf-next v6 7/7] selftests/bpf: Remove tailcalls tests from DENYLIST.riscv64 Pu Lehui
2026-07-21 18:30 ` [PATCH bpf-next v6 0/7] Mixing bpf2bpf and tailcalls for RV64 patchwork-bot+netdevbpf
2026-07-22 3:05 ` Pu Lehui
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=87mrvkus7o.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--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
all inboxes | Powered by JetHome®