From: Stefan Fleischmann <sfle@kth.se>
To: "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
Subject: Re: [REGRESSION] Commit 447cbe95ebb9 causes IOMMU DMA faults on macvlan/vlan with bnxt_en
Date: Mon, 5 Oct 2026 14:54:30 +0200 [thread overview]
Message-ID: <20261005145430.12777c2c@nargothrond> (raw)
In-Reply-To: <CAL4WiioggQU3VtWSL9nrExg5SZZbKiPA8pWmzeH+uRa0gy2ApA@mail.gmail.com>
On Mon, 5 Oct 2026 12:14:00 +0200
Eric Dumazet <edumazet@kernel.org> wrote:
> Le lun. 5 oct. 2026 à 11:44, Fabian Grünbichler
> <f.gruenbichler@proxmox.com> a écrit :
> >
> > On October 5, 2026 3:59 am, Eric Dumazet wrote:
> > >
> > >
> > > On 10/5/26 00:29, Michael Chan wrote:
> > >>
> > >> I think skb->len is not updated with the padded length here. So
> > >> the HW will drop the packet seeing that the length is too short.
> > >> There is another skb_put_padto() that might work better?
> > >
> > > +1 Exactly, thanks!
> >
> > FWIW, we suspect we have quite a few users running into this since
> > importing upstream changes from 7.2.2-7.2.5.
> >
> > Will report back once we've provided those users with a kernel with
> > the below diff.
>
> Patch has been sent for review:
>
> https://lore.kernel.org/netdev/20261005023812.130639-1-edumazet@kernel.org/
I'm testing the patch on v6.18.55, and it looks good so far. 5 hours and
counting without any issues.
Best,
Stefan
next prev parent reply other threads:[~2026-10-05 13:03 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 [this message]
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=20261005145430.12777c2c@nargothrond \
--to=sfle@kth.se \
--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=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