From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "Sasha Levin" <sashal@kernel.org>,
"Eric Dumazet" <edumazet@kernel.org>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Michael Chan <michael.chan@broadcom.com>,
Joe Damato <joe@dama.to>,
netdev@vger.kernel.org, Pavan Chebbi <pavan.chebbi@broadcom.com>,
regressions@lists.linux.dev, stable@vger.kernel.org,
Stefan Fleischmann <sfle@kth.se>
Subject: Re: [REGRESSION] Commit 447cbe95ebb9 causes IOMMU DMA faults on macvlan/vlan with bnxt_en
Date: Wed, 7 Oct 2026 12:33:34 +0200 [thread overview]
Message-ID: <cce34174-a70a-4e59-9c35-fd74309b0fb5@leemhuis.info> (raw)
In-Reply-To: <2026-10-06-1-daily-reply-0020-bnxt-en-vlan-447cbe95@kernel.org>
On 10/6/26 23:35, Sasha Levin wrote:
>> I'm testing the patch on v6.18.55, and it looks good so far. 5 hours and
>> counting without any issues.
>
> Thanks for the bisect. The root cause is the bnxt_en small-packet padding
> and DMA length bug Eric Dumazet identified, not 447cbe95ebb9 ("vlan: fix
> skb_under_panic and races when toggling HW VLAN offload") itself, so we
> will not revert the vlan fix. Once Eric's "bnxt_en: fix DMA mapping length
> for padded small packets" lands in mainline, we will backport it to all
> affected stable trees.
FWIW, better wait a little longer till a fix for another regression
447cbe95ebb9 exposed in another driver is fixed, too:
https://lore.kernel.org/all/CAPa5EdCj3v17tB-SF2JNecq5Q8s1Pranr-XzAFWNpNTBPgPG7w@mail.gmail.com/
Ciao, Thorsten
next prev parent reply other threads:[~2026-10-07 10:44 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
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 [this message]
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=cce34174-a70a-4e59-9c35-fd74309b0fb5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=edumazet@kernel.org \
--cc=f.gruenbichler@proxmox.com \
--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=sashal@kernel.org \
--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