netdev - More wireless problems..

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-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwTGDFgRuPS5DaQ9-XMLgbZ0y6ZtvXLsZhFkM6P_kXQHw@mail.gmail.com>
Date:	Mon, 18 Aug 2014 00:01:30 -0400
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Johannes Berg <johannes.berg@...el.com>,
	Emmanuel Grumbach <emmanuel.grumbach@...el.com>
Cc:	Intel Linux Wireless <ilw@...ux.intel.com>,
	"John W. Linville" <linville@...driver.com>,
	Linux Wireless List <linux-wireless@...r.kernel.org>,
	Network Development <netdev@...r.kernel.org>
Subject: More wireless problems..

So there's still something seriously wrong with the wireless changes
in the current merge window. Maybe it's not new, and is triggered by
something with the hotel wireless here at the kernel summit, but I
just got a NULL pointer dereference:

  BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
  IP: ieee80211_vif_use_reserved_switch+0x71c/0xb00 [mac80211]

this may not be iwl-specific at all, but the second oops (which is
likely just a result of the first one) does end up having iwl-related
functions on the stack , so I'm cc'ing both generic wireless people
and intel wireless people. It's the same machine that showed the intel
wireless scanning microcode problem, but the oops looks very
different.

The end result is a dead machine (when kworkers die, things tend to go
downhill fast), so it would be good to have people give this a good
look.

Attached is the more complete oops details. I don't know what
triggered it, the machine was largely idle.

Ideas?

               Linus

Download attachment "oops" of type "application/octet-stream" (6218 bytes)