This is a note to let you know that I've just added the patch titled
b43: Fix oops on unload when firmware not found
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
b43-fix-oops-on-unload-when-firmware-not-found.patch
and it can be found in the queue-3.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From f89ff6441df06abc2d95f3ef67525923032d6283 Mon Sep 17 00:00:00 2001
From: Larry Finger <[email protected]>
Date: Wed, 24 Oct 2012 08:57:16 -0500
Subject: b43: Fix oops on unload when firmware not found
From: Larry Finger <[email protected]>
commit f89ff6441df06abc2d95f3ef67525923032d6283 upstream.
When b43 fails to find firmware when loaded, a subsequent unload will
oops due to calling ieee80211_unregister_hw() when the corresponding
register call was never made.
Commit 2d838bb608e2d1f6cb4280e76748cb812dc822e7 fixed the same problem
for b43legacy.
Signed-off-by: Larry Finger <[email protected]>
Tested-by: Markus Kanet <[email protected]>
Cc: Markus Kanet <[email protected]>
Signed-off-by: John W. Linville <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/net/wireless/b43/main.c | 2 ++
1 file changed, 2 insertions(+)
--- a/drivers/net/wireless/b43/main.c
+++ b/drivers/net/wireless/b43/main.c
@@ -5430,6 +5430,8 @@ static void b43_ssb_remove(struct ssb_de
cancel_work_sync(&wldev->restart_work);
B43_WARN_ON(!wl);
+ if (!wldev->fw.ucode.data)
+ return; /* NULL if firmware never loaded */
if (wl->current_dev == wldev) {
/* Restore the queues count before unregistering, because
firmware detect
* might have modified it. Restoring is important, so the
networking
Patches currently in stable-queue which might be from [email protected]
are
queue-3.4/b43-fix-oops-on-unload-when-firmware-not-found.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
