From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: akiyano@amazon.com, darinzon@amazon.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, shayagr@amazon.com, harry@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH net] net: ena: Keep the RX buffer mapped if skb allocation fails
Date: Wed, 11 Nov 2026 23:00:07 +0000 [thread overview]
Message-ID: <179443800718.1692642.15271790587054510634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109-ena-rx-skb-alloc-fail-v1-1-aee2927cb51f@debian.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 09 Nov 2026 09:14:29 -0800 you wrote:
> We are seeing the following issue in production on arm64 EC2 hosts
> (m8g.metal-24xl, 64K pages, SMMUv3 in strict mode, 6.18 based kernel).
> Right after a global OOM, the SMMU reports F_TRANSLATION write faults
> from the ENA device, followed by a burst of:
>
> WARNING: CPU: 48 PID: 1656834 at drivers/iommu/dma-iommu.c:1242 iommu_dma_unmap_phys+0xf4/0x108
> Call trace:
> iommu_dma_unmap_phys+0xf4/0x108 (P)
> dma_unmap_phys+0x194/0x2a8
> dma_unmap_page_attrs+0x1c/0x38
> ena_io_poll+0x7bc/0x1790 [ena]
> __napi_poll+0x54/0x220
> net_rx_action+0x250/0x520
>
> [...]
Here is the summary with links:
- [net] net: ena: Keep the RX buffer mapped if skb allocation fails
https://git.kernel.org/netdev/net/c/3e8e22a1007a
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-11-11 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 17:14 Breno Leitao
2026-11-11 23: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=179443800718.1692642.15271790587054510634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=harry@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shayagr@amazon.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
all inboxes | Powered by JetHome®