netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	ilias.apalodimas@linaro.org, jonathan.lemon@gmail.com
Subject: Re: [PATCH net] xdp: fix invalid wait context of page_pool_destroy()
Date: Mon, 15 Jul 2024 04:40:30 +0000	[thread overview]
Message-ID: <172101843035.2749.4308013490462754143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240712095116.3801586-1-ap420073@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 12 Jul 2024 09:51:16 +0000 you wrote:
> If the driver uses a page pool, it creates a page pool with
> page_pool_create().
> The reference count of page pool is 1 as default.
> A page pool will be destroyed only when a reference count reaches 0.
> page_pool_destroy() is used to destroy page pool, it decreases a
> reference count.
> When a page pool is destroyed, ->disconnect() is called, which is
> mem_allocator_disconnect().
> This function internally acquires mutex_lock().
> 
> [...]

Here is the summary with links:
  - [net] xdp: fix invalid wait context of page_pool_destroy()
    https://git.kernel.org/netdev/net/c/59a931c5b732

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-07-15  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  9:51 [PATCH net] xdp: fix invalid wait context of page_pool_destroy() Taehee Yoo
2024-07-13 22:09 ` Jakub Kicinski
2024-07-15  4:40 ` 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=172101843035.2749.4308013490462754143.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ap420073@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=john.fastabend@gmail.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).