[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175807681449.1444719.15338254509817798982.git-patchwork-notify@kernel.org>
Date: Wed, 17 Sep 2025 02:40:14 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Radim Krčmář <rkrcmar@...tanamicro.com>@codeaurora.org
Cc: linux-riscv@...ts.infradead.org, bpf@...r.kernel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
eddyz87@...il.com, song@...nel.org, yonghong.song@...ux.dev,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, bjorn@...nel.org, pulehui@...wei.com,
puranjay@...nel.org, paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, alex@...ti.fr, memxor@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] riscv, bpf: fix reads of thread_info.cpu
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@...nel.org>:
On Tue, 12 Aug 2025 11:02:54 +0200 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [1/2] riscv, bpf: use lw when reading int cpu in BPF_MOV64_PERCPU_REG
https://git.kernel.org/riscv/c/ad5348c76591
- [2/2] riscv, bpf: use lw when reading int cpu in bpf_get_smp_processor_id
https://git.kernel.org/riscv/c/8a16586fa7b8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists