public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: io-uring@vger.kernel.org, dw@davidwei.uk, toke@redhat.com,
	kuba@kernel.org, almasrymina@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH io_uring-6.15] io_uring/zcrx: fix late dma unmap for a dead dev
Date: Tue, 22 Apr 2025 08:57:51 +0000	[thread overview]
Message-ID: <174531227199.1477965.208834710811336342.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ef9b7db249b14f6e0b570a1bb77ff177389f881c.1744965853.git.asml.silence@gmail.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Jens Axboe <axboe@kernel.dk>:

On Fri, 18 Apr 2025 13:02:27 +0100 you wrote:
> There is a problem with page pools not dma-unmapping immediately
> when the device is going down, and delaying it until the page pool is
> destroyed, which is not allowed (see links). That just got fixed for
> normal page pools, and we need to address memory providers as well.
> 
> Unmap pages in the memory provider uninstall callback, and protect it
> with a new lock. There is also a gap between a dma mapping is created
> and the mp is installed, so if the device is killed in between,
> io_uring would be hodling dma mapping to a dead device with no one to
> call ->uninstall. Move it to page pool init and rely on ->is_mapped to
> make sure it's only done once.
> 
> [...]

Here is the summary with links:
  - [io_uring-6.15] io_uring/zcrx: fix late dma unmap for a dead dev
    https://git.kernel.org/bpf/bpf/c/f12ecf5e1c5e

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



      parent reply	other threads:[~2025-04-22  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 12:02 [PATCH io_uring-6.15] io_uring/zcrx: fix late dma unmap for a dead dev Pavel Begunkov
2025-04-18 14:01 ` Jens Axboe
2025-04-22  8:57 ` 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=174531227199.1477965.208834710811336342.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=dw@davidwei.uk \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=toke@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