[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173257383550.4058254.12806548531670345328.git-patchwork-notify@kernel.org>
Date: Mon, 25 Nov 2024 22:30:35 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Larysa Zaremba <larysa.zaremba@...el.com>
Cc: bpf@...r.kernel.org, bjorn@...nel.org, magnus.karlsson@...el.com,
maciej.fijalkowski@...el.com, jonathan.lemon@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, ast@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
horms@...nel.org, przemyslaw.kitszel@...el.com, jacob.e.keller@...el.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
alasdair.mcwilliam@...look.com
Subject: Re: [PATCH bpf] xsk: always clear DMA mapping information when unmapping
the pool
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Fri, 22 Nov 2024 12:29:09 +0100 you wrote:
> When the umem is shared, the DMA mapping is also shared between the xsk
> pools, therefore it should stay valid as long as at least 1 user remains.
> However, the pool also keeps the copies of DMA-related information that are
> initialized in the same way in xp_init_dma_info(), but cleared by
> xp_dma_unmap() only for the last remaining pool, this causes the problems
> below.
>
> [...]
Here is the summary with links:
- [bpf] xsk: always clear DMA mapping information when unmapping the pool
https://git.kernel.org/bpf/bpf/c/ac9a48a6f161
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