From: Eric Dumazet <edumazet@kernel.org>
To: Stefan Fleischmann <sfle@kth.se>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
regressions@lists.linux.dev, Joe Damato <joe@dama.to>
Subject: Re: [REGRESSION] Commit 447cbe95ebb9 causes IOMMU DMA faults on macvlan/vlan with bnxt_en
Date: Sun, 4 Oct 2026 22:52:49 +0200 [thread overview]
Message-ID: <919dcfaa-005f-4bfd-8889-39acda5f7a92@kernel.org> (raw)
In-Reply-To: <20261004192902.3ab3b7f3@nargothrond>
On 10/4/26 19:29, Stefan Fleischmann wrote:
> On Sun, 4 Oct 2026 16:35:32 +0200
> Stefan Fleischmann <sfle@kth.se> wrote:
>
>> On Sun, 4 Oct 2026 13:46:08 +0200
>> Eric Dumazet <edumazet@kernel.org> wrote:
>>
>>
>>>
>>> Notice that 0xfc499000 is on an exact 4KB page boundary. This points
>>> to a DMA read overrun where the Broadcom DMA engine reads past the
>>> end of a buffer mapped in page 0xfc498xxx into the adjacent unmapped
>>> page 0xfc499000.
>>>
>>> Have you tried a recent net kernel ?
>>
>> Hi Eric,
>>
>> that might be a bit tricky. We use ZFS on this server and the version
>> we have installed only supports up to kernel 7.2.
>
> Scratch that, I noticed that this even happens with none of the LXC
> containers running. So I tested with the main branch from
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
> (commit 6dc989ea46b9)
>
> Same issue.
Okay, this must be a bnxt issue, that has been hidden years because of
some skb->data headroom/offset.
LL_RESERVED_SPACE() has been increased from 48 to 64. So perhaps small
packets are now crossing a page boundary (which should be fine)
I see one bug in the skb_pad() vicinity. Could you try:
diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
index
d7728d0c5b6e63ee72de9dea54426bb4c8b7a9fc..f9feeb4471a8cf310788ef8d00b68a1508a7e78e
100644
--- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
+++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
@@ -678,6 +678,7 @@ static netdev_tx_t bnxt_start_xmit(struct sk_buff
*skb, struct net_device *dev)
/* SKB already freed. */
goto tx_kick_pending;
length = BNXT_MIN_PKT_SIZE;
+ len += pad;
}
mapping = dma_map_single(&pdev->dev, skb->data, len,
DMA_TO_DEVICE);
next prev parent reply other threads:[~2026-10-04 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 10:26 [REGRESSION] Commit 447cbe95ebb9 causes IOMMU DMA faults on macvlan/vlan with bnxt_en Stefan Fleischmann
2026-10-04 11:46 ` Eric Dumazet
2026-10-04 14:35 ` Stefan Fleischmann
2026-10-04 17:29 ` Stefan Fleischmann
2026-10-04 20:52 ` Eric Dumazet [this message]
2026-10-04 21:11 ` Eric Dumazet
2026-10-04 22:29 ` Michael Chan
2026-10-05 1:59 ` Eric Dumazet
2026-10-05 9:44 ` Fabian Grünbichler
2026-10-05 10:14 ` Eric Dumazet
2026-10-05 12:54 ` Stefan Fleischmann
2026-10-06 21:35 ` Sasha Levin
2026-10-07 10:33 ` Thorsten Leemhuis
2026-10-07 11:08 ` Eric Dumazet
2026-10-05 17:38 ` Joe Damato
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=919dcfaa-005f-4bfd-8889-39acda5f7a92@kernel.org \
--to=edumazet@kernel.org \
--cc=joe@dama.to \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.com \
--cc=regressions@lists.linux.dev \
--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