mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Huang Fu <leon.huangfu@shopee.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Leon Huang Fu <leon.huangfu@shopee.com>,
	Leon Hwang <leon.hwang@linux.dev>,
	KaFai Wan <kafai.wan@linux.dev>,
	bpf@vger.kernel.org, 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: Wed,  1 Jul 2026 16:04:38 +0800	[thread overview]
Message-ID: <20260701080524.194326-1-leon.huangfu@shopee.com> (raw)
In-Reply-To: <7438f087-7fb4-4991-a095-1d24d6d09895@loongson.cn>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

On Wed, 1 Jul 2026 15:29:28 +0800, Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
> On 2026/7/1 下午3:02, Leon Hwang wrote:
>> On 1/7/26 14:49, Tiezhu Yang wrote:
>> [...]
>>>>
>>>> It is a real issue.
>>>>
>>>> Instead of fixing up helper calls, it seems better to prevent
>>>> interpreter fallback if the prog has any JIT-inlineable helper call.
>>>
>>> Hi Alexei and Leon,
>>>
>>> What about the following: (not tested yet, if it is good, I can test it)
>>>
>>> [...]
>>>
>>> If you are OK with the above changes, I will test it again and send
>>> a new version later.
>>>
>>
>> If you don't mind, I think I can disallow the interpreter fallback by
>> the below diff in the next revision of this series.
>>
>> The 'aux->jit_required' is introduced by following Alexei's suggestion.
>
> I am not sure if introducing a new aux->jit_required member is necessary,
> as we already have a local jit_needed flag in the current logic.

A 'must_jit'-like member was suggested by Alexei [1].

Probably, the commits in [2] could help to understand 'aux->jit_required'.

[1] https://lore.kernel.org/bpf/DJMRIZ5PDWP4.12OOZ8H881H6O@gmail.com/
[2] https://github.com/Asphaltt/bpf/commits/bpf/fix-interpreter-fallback/v2/

>
> Additionally, the issue reported in my patch [1] is fundamentally tied
> to bpf_jit_inlines_helper_call(). Maybe we can simply reuse jit_needed
> by checking bpf_prog_has_inline_helpers() right before JITing, and then
> reject fallback with -ENOTSUPP if JIT compilation fails.

Correct. Reusing jit_needed is preferred.

Thanks,
Leon

>
> Let us wait for Alexei's comments on the overall direction before
> respinning.
>
> [1] bpf: Fix unaligned interpreter panic on JIT fallback path
> https://lore.kernel.org/bpf/20260615025316.24429-1-yangtiezhu@loongson.cn/
>
> Thanks,
> Tiezhu

  reply	other threads:[~2026-07-01  8:11 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
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 [this message]
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=20260701080524.194326-1-leon.huangfu@shopee.com \
    --to=leon.huangfu@shopee.com \
    --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=leon.hwang@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