LoongArch architecture development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, kafai.wan@linux.dev, bpf@vger.kernel.org,
	loongarch@lists.linux.dev, leon.hwang@linux.dev,
	puranjay@kernel.org, bjorn@kernel.org
Subject: Re: [PATCH bpf-next v9 0/2] Introduce jit_required to prevent a kernel panic
Date: Thu, 09 Jul 2026 06:30:08 +0000	[thread overview]
Message-ID: <178357860889.3274983.15989221425379475238.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708101806.18885-1-yangtiezhu@loongson.cn>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:

On Wed,  8 Jul 2026 18:18:04 +0800 you wrote:
> This series introduces a 'jit_required' flag in struct bpf_prog
> to track programs that strictly require JIT.
> 
> The aim is to prevent a kernel panic by rejecting programs with
> inlined helpers when JIT is not available.
> 
> v8 -> v9:
>   -- Initialize 'fp->jit_required' with
>      'IS_ENABLED(CONFIG_BPF_JIT_ALWAYS_ON)'
>      in bpf_prog_alloc_no_stats()
>   -- Simplify __bpf_prog_select_runtime()
>   -- Simplify the commit description for patch 1
>   -- Enhance the commit description for patch 2
> 
> [...]

Here is the summary with links:
  - [bpf-next,v9,1/2] bpf: Introduce jit_required flag and remove bpf_prog_has_kfunc_call()
    https://git.kernel.org/bpf/bpf-next/c/9a6df65d5c6a
  - [bpf-next,v9,2/2] bpf: Reject programs with inlined helpers if JIT is not available
    https://git.kernel.org/bpf/bpf-next/c/f1c27922576e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-09  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 10:18 [PATCH bpf-next v9 0/2] Introduce jit_required to prevent a kernel panic Tiezhu Yang
2026-07-08 10:18 ` [PATCH bpf-next v9 1/2] bpf: Introduce jit_required flag and remove bpf_prog_has_kfunc_call() Tiezhu Yang
2026-07-08 10:18 ` [PATCH bpf-next v9 2/2] bpf: Reject programs with inlined helpers if JIT is not available Tiezhu Yang
2026-07-08 10:59   ` bot+bpf-ci
2026-07-09  3:36     ` Tiezhu Yang
2026-07-08 14:06 ` [PATCH bpf-next v9 0/2] Introduce jit_required to prevent a kernel panic Leon Hwang
2026-07-09  6:30 ` patchwork-bot+netdevbpf [this message]

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=178357860889.3274983.15989221425379475238.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=jolsa@kernel.org \
    --cc=kafai.wan@linux.dev \
    --cc=leon.hwang@linux.dev \
    --cc=loongarch@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=puranjay@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