linux-kernel - Regression in 2.6.30-rc1 since commit acae0515

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

Message-ID: <49DC2DF5.3010603@lwfinger.net>
Date:	Tue, 07 Apr 2009 23:54:13 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Arjan van de Ven <arjan@...ux.intel.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	wireless <linux-wireless@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Regression in 2.6.30-rc1 since commit acae0515 - wireless broken

The most recent pulls of the Linux-2.6 git tree has broken wireless. The problem
was bisected with commit acae05156551fd7528fbb616271e672789388e3c, entitled
"module: create a request_module_nowait()", indicated as the faulty change. This
is seen with driver b43 on my system, and 2 reports for driver iwlagn:
http://marc.info/?l=linux-wireless&m=123916157630571&w=2 and
http://marc.info/?l=linux-wireless&m=123913015021457&w=2.

For b43, the logged error messages are:

phy0: Failed to initialize wep: -2
b43: probe of ssb0:0 failed with error -2

With this driver, module ssb is selected from the PCI ID. It then loads b43,
which triggers the loading of rfkill, mac80211, cfg80211, led-class, and
input-polldev. It appears that the nowait method is killing the chain somewhere.
If I unload and reload b43, then all these modules load correctly and wireless
works.

If this commit is reverted, wireless works OK.

I will be happy to try any patches to make request_module_nowait() work with
wireless networking.

Larry

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/