From: Leon Hwang <leon.hwang@linux.dev>
To: KaFai Wan <kafai.wan@linux.dev>,
bpf@vger.kernel.org, Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Anton Protopopov <a.s.protopopov@gmail.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [RFC PATCH bpf 1/6] bpf: Disallow interpreter fallback for user BPF_ADDR_SPACE_CAST insn
Date: Tue, 30 Jun 2026 22:36:12 +0800 [thread overview]
Message-ID: <a2aaa21d-4cf9-48a4-839f-dd152bda8185@linux.dev> (raw)
In-Reply-To: <e279c9a7ca6b16e52dc261560513b0eafdd70f87.camel@linux.dev>
On 2026/6/30 22:29, KaFai Wan wrote:
> On Fri, 2026-06-26 at 23:43 +0800, Leon Hwang wrote:
[...]
>> /* Fix up helper call offsets on JIT fallback path. */
>> -static void bpf_fixup_fallback_helpers(struct bpf_verifier_env *env, struct bpf_prog *fp)
>> +static int bpf_fixup_fallback_helpers(struct bpf_verifier_env *env, struct bpf_prog *fp)
>> {
>> struct bpf_insn *insn = fp->insnsi;
>> const struct bpf_func_proto *fn;
>> int i;
>>
>> - if (!env || !env->ops->get_func_proto)
>> - return;
>> + if (!env)
>> + return 0;
>>
>> for (i = 0; i < fp->len; i++, insn++) {
>> - if (bpf_helper_call(insn) && bpf_jit_inlines_helper_call(insn->imm)) {
>> + if (env->ops->get_func_proto && bpf_helper_call(insn) &&
>> + bpf_jit_inlines_helper_call(insn->imm)) {
>> fn = env->ops->get_func_proto(insn->imm, env->prog);
>> if (fn && fn->func)
>> insn->imm = fn->func - __bpf_call_base;
> It might be better to use the BPF_CALL_IMM macro. insn->imm = BPF_CALL_IMM(fn->func);
Makes sense.
This might be applied to Tiezhu's patch.
Thanks,
Leon
>> }
>> +
>> + if (bpf_insn_requires_jit(insn))
>> + return -EOPNOTSUPP;
>> }
>> [...]
next prev parent reply other threads:[~2026-06-30 14:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:43 [RFC PATCH bpf 0/6] bpf: Disallow interpreter fallback for interpreter-unsupported insns Leon Hwang
2026-06-26 15:43 ` [RFC PATCH bpf 1/6] bpf: Disallow interpreter fallback for user BPF_ADDR_SPACE_CAST insn Leon Hwang
2026-06-30 14:29 ` KaFai Wan
2026-06-30 14:36 ` Leon Hwang [this message]
2026-07-01 1:26 ` Tiezhu Yang
2026-07-01 6:21 ` Leon Hwang
2026-07-01 6:49 ` Tiezhu Yang
2026-07-01 7:02 ` Leon Hwang
2026-07-01 7:29 ` Tiezhu Yang
2026-07-01 8:04 ` Leon Huang Fu
2026-07-01 9:07 ` Tiezhu Yang
2026-07-01 18:47 ` Alexei Starovoitov
2026-06-26 15:43 ` [RFC PATCH bpf 2/6] bpf: Disallow interpreter fallback for arena insn Leon Hwang
2026-06-26 15:43 ` [RFC PATCH bpf 3/6] bpf: Disallow interpreter fallback for BPF_MOV64_PERCPU_REG insn Leon Hwang
2026-06-26 15:43 ` [RFC PATCH bpf 4/6] bpf: Disallow interpreter fallback for internal BPF_PROBE_ATOMIC insn Leon Hwang
2026-06-26 15:43 ` [RFC PATCH bpf 5/6] bpf: Disallow interpreter fallback for gotox insn Leon Hwang
2026-06-26 15:43 ` [RFC PATCH bpf 6/6] lib/test_bpf: Add interpreter-fallback tests Leon Hwang
2026-06-26 16:11 ` [RFC PATCH bpf 0/6] bpf: Disallow interpreter fallback for interpreter-unsupported insns Leon Hwang
2026-06-30 23:12 ` Alexei Starovoitov
2026-07-01 2:59 ` Leon Hwang
2026-07-01 3:05 ` Leon Hwang
2026-07-01 5:50 ` Alexei Starovoitov
2026-07-01 6:20 ` Leon Hwang
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=a2aaa21d-4cf9-48a4-839f-dd152bda8185@linux.dev \
--to=leon.hwang@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=akpm@linux-foundation.org \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai.wan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yangtiezhu@loongson.cn \
--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