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
| ||
|
Message-ID: <87o9v99r3g.fsf@purkki.adurom.net> Date: Thu, 04 May 2017 07:35:31 +0300 From: Kalle Valo <kvalo@...eaurora.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: David Miller <davem@...emloft.net>, Johannes Berg <johannes@...solutions.net>, Linux Wireless List <linux-wireless@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Luca Coelho <luciano.coelho@...el.com> Subject: Re: new warning at net/wireless/util.c:1236 Linus Torvalds <torvalds@...ux-foundation.org> writes: > So my Dell XPS 13 seems to have grown a new warning as of the > networking merge yesterday. > > Things still work, but when it starts warning, it generates a *lot* of > noise (I got 36 of these within about ten minutes). > > I have no idea what triggered it, because when I rebooted (not because > of this issue, but just to reboot into a newer kernel) I don't see it > again. > > This is all pretty regular wireless - it's intel 8260 wireless in a > fairly normal laptop. > > Things still seem to *work* ok, so the only problem here is the overly > verbose and useless WARN_ON. It doesn't even print out *which* rate it > is warning about, it just does that stupid unconditional WARN_ON() > without ever shutting up about it.. > > The WARN_ON() seems to be old, but my logs don't seem to have any > mention of this until today, so there's something that has changed > that now triggers it. > > Ideas? > > Linus > > --- > > WARNING: CPU: 3 PID: 1138 at net/wireless/util.c:1236 > cfg80211_calculate_bitrate+0x139/0x170 [cfg80211] As this is with iwlwifi adding also Luca. There were some rate handling changes in iwlwifi, like commit 77e409455f41, but don't know if that could cause this. -- Kalle Valo
Powered by blists - more mailing lists