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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 12 Feb 2022 16:10:08 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Toke Høiland-Jørgensen <toke@...hat.com>@ci.codeaurora.org Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org, memxor@...il.com, zhguan@...hat.com, netdev@...r.kernel.org, bpf@...r.kernel.org Subject: Re: [PATCH bpf-next v2] libbpf: Use dynamically allocated buffer when receiving netlink messages Hello: This patch was applied to bpf/bpf-next.git (master) by Andrii Nakryiko <andrii@...nel.org>: On Sat, 12 Feb 2022 00:48:19 +0100 you wrote: > When receiving netlink messages, libbpf was using a statically allocated > stack buffer of 4k bytes. This happened to work fine on systems with a 4k > page size, but on systems with larger page sizes it can lead to truncated > messages. The user-visible impact of this was that libbpf would insist no > XDP program was attached to some interfaces because that bit of the netlink > message got chopped off. > > [...] Here is the summary with links: - [bpf-next,v2] libbpf: Use dynamically allocated buffer when receiving netlink messages https://git.kernel.org/bpf/bpf-next/c/9c3de619e13e 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