From: patchwork-bot+netdevbpf@kernel.org
To: Hasan Basbunar <basbunarhasan@gmail.com>
Cc: hawk@kernel.org, ilias.apalodimas@linaro.org, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
horms@kernel.org, almasrymina@google.com, asml.silence@gmail.com,
kaiyuanz@google.com, willemb@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] page_pool: fix memory-provider leak in page_pool_create_percpu() error path
Date: Thu, 30 Apr 2026 04:10:05 +0000 [thread overview]
Message-ID: <177752220554.2344375.3558591784501370664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260428170739.34881-1-basbunarhasan@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Apr 2026 19:07:39 +0200 you wrote:
> When page_pool_create_percpu() fails on page_pool_list(), it falls
> through to its err_uninit: label, which calls page_pool_uninit().
> At that point page_pool_init() has already taken two references
> when the user requested PP_FLAG_ALLOW_UNREADABLE_NETMEM:
>
> pool->mp_ops->init(pool)
> static_branch_inc(&page_pool_mem_providers);
>
> [...]
Here is the summary with links:
- page_pool: fix memory-provider leak in page_pool_create_percpu() error path
https://git.kernel.org/netdev/net/c/5ef343614db7
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:[~2026-04-30 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 17:07 [PATCH] page_pool: fix memory-provider leak in page_pool_create_percpu() error path Hasan Basbunar
2026-04-30 4:10 ` 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=177752220554.2344375.3558591784501370664.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=basbunarhasan@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kaiyuanz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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