From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Nicolas Escande" <nico.escande@gmail.com>,
nbd@nbd.name, "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Kalle Valo" <kvalo@kernel.org>,
"Johannes Berg" <johannes.berg@intel.com>
Cc: linux-wireless@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: [regression] STP on 80211s is broken in 6.4-rc4
Date: Sat, 10 Jun 2023 13:44:03 +0700 [thread overview]
Message-ID: <ZIQbs0wqdRh7c0Kx@debian.me> (raw)
In-Reply-To: <CT5GNZSK28AI.2K6M69OXM9RW5@syracuse>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
On Tue, Jun 06, 2023 at 12:55:57PM +0200, Nicolas Escande wrote:
> Hello Felix,
>
> As user of the mesh part of mac80211 on multiple products at work let me say
> thank you for all the work you do on wifi, especially on 80211s, and especially
> the recent improvements you made for mesh fast RX/TX & cross vendor AMSDU compat
>
> We upgraded our kernel from an older (5.15) to a newer 6.4. The problem is STP
> doesn't work anymore and alas we use it for now (for the better or worse).
>
> What I gathered so far from my setup:
> - we use ath9k & ath10k
> - in my case STP frames are received as regular packet and not as amsdu
> - the received packets have a wrong length of 44 in tcpdump
> (instead of 38 with our previous kernel)
> - llc_fixup_skb() tries to pull some 41 bytes out of a 35 bytes packet
> this makes llc_rcv() discard the frames & breaks STP
>
> >From bisecting the culprit seems to be 986e43b19ae9176093da35e0a844e65c8bf9ede7
> (wifi: mac80211: fix receiving A-MSDU frames on mesh interfaces)
>
> I guess that your changes to handle both ampdu subframes & normal frames in the
> same datapath ends up putting a wrong skb->len for STP (multicast) frames ?
> Honestly I don't understand enough of the 80211 internals & spec to pinpoint the
> exact problem.
>
> It seems this change was already in the 6.3 kernel so I guess someone should
> have seen it before (but I didn't find anything..) ? Maybe I missed something...
>
> Anyway I'm happy to provide more info or try anything you throw at me.
>
Thanks for the regression report. I'm adding it to regzbot:
(Felix: it looks like this regression is introcued by a commit authored by you.
Would you like to take a look on it?)
#regzbot ^introduced: 986e43b19ae917
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-10 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:55 [regression] STP on 80211s is broken in 6.4-rc4 Nicolas Escande
2023-06-10 6:44 ` Bagas Sanjaya [this message]
2023-06-15 12:54 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-16 7:45 ` Nicolas Escande
2023-06-16 9:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-16 12:17 ` Bagas Sanjaya
2023-06-16 12:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 11:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 16:50 ` Nicolas Escande
2023-07-11 11:12 ` Felix Fietkau
2023-07-11 12:15 ` Nicolas Escande
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=ZIQbs0wqdRh7c0Kx@debian.me \
--to=bagasdotme@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=nico.escande@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=toke@toke.dk \
/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;
as well as URLs for NNTP newsgroup(s).