From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, vbabka@suse.cz,
bpf@vger.kernel.org, eric.dumazet@gmail.com, davem@davemloft.net,
pabeni@redhat.com, linux-mm@kvack.org, akpm@linux-foundation.org,
mgorman@techsingularity.net, willy@infradead.org,
kernel-team@cloudflare.com
Subject: Re: [PATCH net-next] mm/page_pool: catch page_pool memory leaks
Date: Sun, 26 Nov 2023 15:20:25 +0000 [thread overview]
Message-ID: <170101202556.2351.9731751321598377957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <170082101266.1085481.12199867179160710331.stgit@firesoul>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Nov 2023 11:16:52 +0100 you wrote:
> Pages belonging to a page_pool (PP) instance must be freed through the
> PP APIs in-order to correctly release any DMA mappings and release
> refcnt on the DMA device when freeing PP instance. When PP release a
> page (page_pool_release_page) the page->pp_magic value is cleared.
>
> This patch detect a leaked PP page in free_page_is_bad() via
> unexpected state of page->pp_magic value being PP_SIGNATURE.
>
> [...]
Here is the summary with links:
- [net-next] mm/page_pool: catch page_pool memory leaks
https://git.kernel.org/netdev/net-next/c/dba1b8a7ab68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-26 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:16 Jesper Dangaard Brouer
2023-11-26 15:20 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170101202556.2351.9731751321598377957.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hawk@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox