Re: [PATCH bpf-next] riscv, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args
| Newsgroups | org.infradead.lists.linux-riscv,org.kernel.vger.bpf,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178672560540.3871347.8662836444766849077.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to bpf/bpf-next.git (master) by Daniel Borkmann <[email protected]>: On Fri, 14 Aug 2026 06:47:26 +0000 you wrote: > From: Pu Lehui <[email protected]> > > On RV64, the ABI requires sign-extension for signed 1-byte and 2-byte > kfunc args. However, the RV64 JIT currently does not perform > sign-extension for such kfunc args. > > Before commit 7ce090afbf72 ("bpf: Infer zext_dst based on static > register liveness analysis"), state pruning could potentially omit > zero-extension of 32-bit subregisters, which inadvertently masked the > above issue by making the args appear as if they had been properly > sign-extended. After that commit, the problem is exposed, causing the > kfunc_call/kfunc_call_test4 selftest to fail. > > [...] Here is the summary with links: - [bpf-next] riscv, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args https://git.kernel.org/bpf/bpf-next/c/f2aaa6215910 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv