From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, stable@vger.kernel.org,
sfle@kth.se, edumazet@google.com, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, andrew+netdev@lunn.ch,
berni@debian.org, joe@dama.to
Subject: Re: [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets
Date: Thu, 08 Oct 2026 01:00:08 +0000 [thread overview]
Message-ID: <179142120877.3755089.7300655408899224651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007051747.455273-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Oct 2026 07:17:47 +0200 you wrote:
> Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412
> NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:
>
> DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000
> [fault reason 0x06] PTE Read access is not set
> bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001
> ...
> NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out
>
> [...]
Here is the summary with links:
- [v3,net] bnxt_en: fix DMA mapping length for padded small packets
https://git.kernel.org/netdev/net/c/a51d233ccd48
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-10-08 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 5:17 [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets Eric Dumazet
2026-10-07 22:58 ` Michael Chan
2026-10-07 23:14 ` Joe Damato
2026-10-08 1: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=179142120877.3755089.7300655408899224651.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=berni@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sfle@kth.se \
--cc=stable@vger.kernel.org \
/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