hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

wl1271: Check vif for NULL when indicating beacon-loss 

Because the interface is started and the vif are created and destroyed
separately, there is a slim possibility beacon-loss indications occur while
there is no vif - causing a kernel-oops unless checked.

Add checking for the vif.

Signed-off-by: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com>
Signed-off-by: Luciano Coelho <luciano.coelho@nokia.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
Juuso Oikarinen 2009-12-11 15:41:09 +02:00 committed by John W. Linville
parent 38ad2d87d4
commit 04477bf095
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/net/wireless/wl12xx/wl1271_event.c
View File

@ -150,7 +150,7 @@ static int wl1271_event_process(struct wl1271 *wl, struct event_mailbox *mbox)
return ret; return ret;
} }
if (beacon_loss) { if (wl->vif && beacon_loss) {
/* Obviously, it's dangerous to release the mutex while /* Obviously, it's dangerous to release the mutex while
we are holding many of the variables in the wl struct. we are holding many of the variables in the wl struct.
That's why it's done last in the function, and care must That's why it's done last in the function, and care must