[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250617063206.24733-1-yangtiezhu@loongson.cn>
Date: Tue, 17 Jun 2025 14:32:06 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>
Cc: Hengqi Chen <hengqi.chen@...il.com>,
bpf@...r.kernel.org,
loongarch@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: [PATCH bpf-next] LoongArch, bpf: Set bpf_jit_bypass_spec_v1/v4()
JITs can set bpf_jit_bypass_spec_v1/v4() if they want the verifier
to skip analysis/patching for the respective vulnerability, it is
safe to set both bpf_jit_bypass_spec_v1/v4(), because there is no
speculation barrier instruction for LoongArch.
Suggested-by: Luis Gerhorst <luis.gerhorst@....de>
Signed-off-by: Tiezhu Yang <yangtiezhu@...ngson.cn>
---
This is based on the latest bpf-next tree which contains the
prototype and caller for bpf_jit_bypass_spec_v1/v4().
By the way, it needs to update bpf-next tree before building
on LoongArch:
[Build Error Report] Implicit Function declaration for bpf-next tree
https://lore.kernel.org/bpf/d602ae87-8bed-1633-d5b6-41c5bd8bbcdc@loongson.cn/
arch/loongarch/net/bpf_jit.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/loongarch/net/bpf_jit.c b/arch/loongarch/net/bpf_jit.c
index fa1500d4aa3e..5de8f4c44700 100644
--- a/arch/loongarch/net/bpf_jit.c
+++ b/arch/loongarch/net/bpf_jit.c
@@ -1359,3 +1359,13 @@ bool bpf_jit_supports_subprog_tailcalls(void)
{
return true;
}
+
+bool bpf_jit_bypass_spec_v1(void)
+{
+ return true;
+}
+
+bool bpf_jit_bypass_spec_v4(void)
+{
+ return true;
+}
--
2.42.0
Powered by blists - more mailing lists