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: Mon, 11 Apr 2022 15:40:11 +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, davem@...emloft.net, kuba@...nel.org, hawk@...nel.org, freysteinn.alfredsson@....se, pabeni@...hat.com, netdev@...r.kernel.org, bpf@...r.kernel.org Subject: Re: [PATCH bpf] bpf: Fix release of page_pool in BPF_PROG_RUN Hello: This patch was applied to bpf/bpf.git (master) by Daniel Borkmann <daniel@...earbox.net>: On Sat, 9 Apr 2022 23:30:53 +0200 you wrote: > The live packet mode in BPF_PROG_RUN allocates a page_pool instance for > each test run instance and uses it for the packet data. On setup it creates > the page_pool, and calls xdp_reg_mem_model() to allow pages to be returned > properly from the XDP data path. However, xdp_reg_mem_model() also raises > the reference count of the page_pool itself, so the single > page_pool_destroy() count on teardown was not enough to actually release > the pool. To fix this, add an additional xdp_unreg_mem_model() call on > teardown. > > [...] Here is the summary with links: - [bpf] bpf: Fix release of page_pool in BPF_PROG_RUN https://git.kernel.org/bpf/bpf/c/425d239379db 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