Netdev List
 help / color / mirror / Atom feed
From: Stefan Fleischmann <sfle@kth.se>
To: Eric Dumazet <edumazet@kernel.org>
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 16:35:32 +0200	[thread overview]
Message-ID: <20261004163532.3134dd41@nargothrond> (raw)
In-Reply-To: <f0c52ecb-b85d-4a53-8329-a8d2fd5d72b8@kernel.org>

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.

> Could you please test whether disabling TSO or hardware VLAN offload 
> prevents the crash? (maybe adding one option at a time)
> 
>    # ethtool -K eno1np0 tso off
> 
>    # ethtool -K eno1np0 tx-vlan-offload off

I tested this now and none of these options made a difference. I've also
tested disabling other offloads, no difference.

Best,
Stefan

> Adding Joe to this thread, because some parts in
> tso_dma_map_init() or tso_start() might have bugs.
> 
> # Disable USO on the physical interface
> ethtool -K eno1np0 tx-udp-segmentation off
> 
> This reminds me on a prior attempt I made months ago to sanitize
> tso_start()
> 
> Note that my email address has changed to edumazet@kernel.org
> 
> Thanks.
> 

  reply	other threads:[~2026-10-04 14:35 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 [this message]
2026-10-04 17:29     ` Stefan Fleischmann
2026-10-04 20:52       ` Eric Dumazet
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=20261004163532.3134dd41@nargothrond \
    --to=sfle@kth.se \
    --cc=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=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