netdev - RE: v5.5-rc1 and beyond insta-kills some Comcast wifi routers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 4 Mar 2020 05:16:37 +0000
From:   Tony Chuang <yhchuang@...ltek.com>
To:     Kalle Valo <kvalo@...eaurora.org>,
        Randy Dunlap <rdunlap@...radead.org>
CC:     "Mancini, Jason" <Jason.Mancini@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: RE: v5.5-rc1 and beyond insta-kills some Comcast wifi routers

Kalle Valo <kvalo@...eaurora.org> writes:
> 
> Randy Dunlap <rdunlap@...radead.org> writes:
> 
> > [add netdev mailing list + 2 patch signers]
> 
> Adding also linux-wireless. It's always best to send questions about any
> wireless issues to linux-wireless
> 
> > On 3/3/20 7:34 PM, Mancini, Jason wrote:
> >> [I can't seem to access the linux-net ml per kernel.org faq, apology
> >> in advance.]
> >>
> >> This change, which I think first appeared for v5.5-rc1, basically
> >> within seconds, knocks out our [apparently buggy] Comcast wifi for
> >> about 2-3 minutes.  Is there a boot option (or similar) where I can
> >> achieve prior kernel behavior?  Otherwise I am stuck on kernel 5.4
> >> (or Win10) it seems, or forever compiling custom kernels for my
> >> choice of distribution [as I don't have physical access to the router
> >> in question.]
> >> Thanks!
> >> Jason
> >>
> >> ================
> >>
> >> 127eef1d46f80056fe9f18406c6eab38778d8a06 is the first bad commit
> >> commit 127eef1d46f80056fe9f18406c6eab38778d8a06
> >> Author: Yan-Hsuan Chuang <yhchuang@...ltek.com>
> >> Date:   Wed Oct 2 14:35:23 2019 +0800
> 
> Can you try if this fixes it:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.gi
> t/commit/?id=74c3d72cc13401f9eb3e3c712855e9f8f2d2682b
> 

Kalle is providing the right possible patch to fix it.

The first bad commit you found, that causes this issue, introduced TX-AMSDU.
But we found that enabling TX-AMSDU on 2.4G band is not working while
connecting to some APs. So, you can try if the patch provided by Kalle works.
(I hope so). Otherwise, you can enable the kernel log debug mask by:
echo 0xffffffff > /sys/module/rtw88/parameters/debug_mask.
And collect the log to see if there's anything wrong.

Yen-Hsuan