From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Yazhou Tang" <tangyazhou@zju.edu.cn>
Cc: "bpf" <bpf@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Eduard" <eddyz87@gmail.com>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Puranjay Mohan" <puranjay@kernel.org>,
"Xu Kuohai" <xukuohai@huaweicloud.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"John Fastabend" <john.fastabend@gmail.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"KP Singh" <kpsingh@kernel.org>,
"Stanislav Fomichev" <sdf@fomichev.me>,
"Hao Luo" <haoluo@google.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Yazhou Tang" <tangyazhou518@outlook.com>,
"Shenghao Yuan" <shenghaoyuan0928@163.com>,
"Tianci Cao" <ziye@zju.edu.cn>
Subject: Re: [PATCH bpf v6 1/2] bpf: Fix s16 truncation for large bpf-to-bpf call offsets
Date: Mon, 20 Apr 2026 08:05:15 -0700 [thread overview]
Message-ID: <DHY2PEXH9GEA.1XOIVBFWLLFIV@gmail.com> (raw)
In-Reply-To: <34a15577-6624-4bbc-a435-17b67e50d2db@zju.edu.cn>
On Mon Apr 20, 2026 at 2:21 AM PDT, Yazhou Tang wrote:
> Hi Alexei,
>
> A gentle ping on this thread.
Do not top post.
> If you don't have a strong preference regarding the target tree,
> my plan is to rebase this patchset onto the bpf-next tree to
> resolve the conflict with bpf_find_subprog().
>
> I will also include the fix for the run-time OOB read caught by
> Sashiko, and send out v7 later this week. Please let me know if
> you'd prefer me to take a different approach.
yes. thanks
next prev parent reply other threads:[~2026-04-20 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 17:03 [PATCH bpf v6 0/2] bpf: Fix s16 truncation for large bpf-to-bpf call offsets Yazhou Tang
2026-04-12 17:03 ` [PATCH bpf v6 1/2] " Yazhou Tang
2026-04-12 20:13 ` Alexei Starovoitov
2026-04-13 2:38 ` Yazhou Tang
2026-04-20 9:21 ` Yazhou Tang
2026-04-20 15:05 ` Alexei Starovoitov [this message]
2026-04-12 17:03 ` [PATCH bpf v6 2/2] selftests/bpf: Add test for large offset bpf-to-bpf call Yazhou Tang
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=DHY2PEXH9GEA.1XOIVBFWLLFIV@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--cc=shenghaoyuan0928@163.com \
--cc=song@kernel.org \
--cc=tangyazhou518@outlook.com \
--cc=tangyazhou@zju.edu.cn \
--cc=xukuohai@huaweicloud.com \
--cc=yonghong.song@linux.dev \
--cc=ziye@zju.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.