lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 08 Mar 2022 14:50:09 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Shung-Hsi Yu <shung-hsi.yu@...e.com> Cc: bpf@...r.kernel.org, linux-kernel@...r.kernel.org, ast@...nel.org, daniel@...earbox.net, andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org, netdev@...r.kernel.org Subject: Re: [PATCH bpf-next] bpf: determine buf_info inside check_buffer_access() Hello: This patch was applied to bpf/bpf-next.git (master) by Daniel Borkmann <daniel@...earbox.net>: On Mon, 7 Mar 2022 13:29:18 +0800 you wrote: > Instead of determining buf_info string in the caller of > check_buffer_access(), we can determine whether the register type is read-only > through type_is_rdonly_mem() helper inside check_buffer_access() and construct > buf_info, making the code slightly cleaner. > > Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@...e.com> > > [...] Here is the summary with links: - [bpf-next] bpf: determine buf_info inside check_buffer_access() https://git.kernel.org/bpf/bpf-next/c/44e9a741cad8 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