[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250812090256.757273-2-rkrcmar@ventanamicro.com>
Date: Tue, 12 Aug 2025 11:02:54 +0200
From: Radim Krčmář <rkrcmar@...tanamicro.com>
To: bpf@...r.kernel.org
Cc: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>,
Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>,
Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>,
Björn Töpel <bjorn@...nel.org>,
Pu Lehui <pulehui@...wei.com>,
Puranjay Mohan <puranjay@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alex@...ti.fr>,
Kumar Kartikeya Dwivedi <memxor@...il.com>,
linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] riscv, bpf: fix reads of thread_info.cpu
Hello,
These patches are related to a recently queued series [1] that fixes the
same bugs in normal code. That series finishes with a patch that would
have exposed the BPF bugs, but luckily it won't get merged until v6.18.
I don't know enough about BPF to verify that it emits the correct code
now, so any pointers are welcome.
1: https://lore.kernel.org/linux-riscv/20250725165410.2896641-3-rkrcmar@ventanamicro.com/
Radim Krčmář (2):
riscv, bpf: use lw when reading int cpu in BPF_MOV64_PERCPU_REG
riscv, bpf: use lw when reading int cpu in bpf_get_smp_processor_id
arch/riscv/net/bpf_jit_comp64.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.50.0
Powered by blists - more mailing lists