netdev - Re: mac80211/ath11k regression in next-20220720

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Fri, 22 Jul 2022 10:05:21 +0200
From:   Johan Hovold <johan@...nel.org>
To:     Johannes Berg <johannes@...solutions.net>
Cc:     Kalle Valo <kvalo@...nel.org>, ath11k@...ts.infradead.org,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: mac80211/ath11k regression in next-20220720

On Fri, Jul 22, 2022 at 09:54:57AM +0200, Johannes Berg wrote:
> On Fri, 2022-07-22 at 09:52 +0200, Johan Hovold wrote:
> > Hi,
> > 
> > After moving from next-20220714 to next-20220720, ath11k stopped
> > working here and instead spits out a bunch of warnings (see log below).
> > 
> > I noticed that this series from Johannes was merged in that period:
> > 
> > 	https://lore.kernel.org/all/20220713094502.163926-1-johannes@sipsolutions.net/
> > 
> > but can't say for sure that it's related. I also tried adding the
> > follow-up fixes from the mld branch:
> > 
> > 	https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/?h=mld
> > 
> > but it didn't seem to make any difference.
> > 
> > Any ideas about what might be going on here?
> > 
> 
> We think the "fix" is this:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?h=mld&id=dd5a559d8e90fdb9424e0580b91702c5838928dc
> 
> Do you want to try it?

Thanks for the quick reply. And yes, that fixes the problem.

I apparently failed to apply all commits from that mld branch, but this
one alone fixes it.

> Note that if that fixes it, it's still a bug in the driver, but one that
> you'd otherwise not hit.

Yeah, those warnings looked like secondary issues if that's what you're
referring to?
 
> Anyway I'll do some tree shuffling today and get that in.

Thanks!

Johan