BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Malov <ivan.malov@oktetlabs.ru>
Cc: magnus.karlsson@intel.com, bjorn.topel@intel.com,
	netdev@vger.kernel.org, andrew.rybchenko@oktetlabs.ru,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	bjorn@kernel.org, maciej.fijalkowski@intel.com,
	jonathan.lemon@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
	john.fastabend@gmail.com, maximmi@mellanox.com
Subject: Re: [PATCH net v3 1/1] xsk: clear page contiguity bit when unmapping pool
Date: Tue, 28 Jun 2022 21:00:14 +0000	[thread overview]
Message-ID: <165645001434.24528.16734258366303906334.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220628091848.534803-1-ivan.malov@oktetlabs.ru>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Tue, 28 Jun 2022 12:18:48 +0300 you wrote:
> When a XSK pool gets mapped, xp_check_dma_contiguity() adds bit 0x1
> to pages' DMA addresses that go in ascending order and at 4K stride.
> The problem is that the bit does not get cleared before doing unmap.
> As a result, a lot of warnings from iommu_dma_unmap_page() are seen
> in dmesg, which indicates that lookups by iommu_iova_to_phys() fail.
> 
> Fixes: 2b43470add8c ("xsk: Introduce AF_XDP buffer allocation API")
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] xsk: clear page contiguity bit when unmapping pool
    https://git.kernel.org/bpf/bpf/c/512d1999b8e9

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



      parent reply	other threads:[~2022-06-28 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 19:01 [PATCH] xsk: clear page contiguity bit when unmapping pool Ivan Malov
2022-06-28  0:17 ` [PATCH v2 1/1] " Ivan Malov
2022-06-28  7:47   ` Magnus Karlsson
2022-06-28  9:18 ` [PATCH net v3 " Ivan Malov
2022-06-28  9:29   ` Magnus Karlsson
2022-06-28 21:00   ` 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=165645001434.24528.16734258366303906334.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=ast@kernel.org \
    --cc=bjorn.topel@intel.com \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=ivan.malov@oktetlabs.ru \
    --cc=john.fastabend@gmail.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=maximmi@mellanox.com \
    --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