wlcore: fixes for connection_loss_work

Browse source

We can't use cancel_delayed_work_sync() from functions that take the
wl->mutex, since connection_loss_work also takes the mutex. This might
result in a deadlock. Restructure the code so the work is synchronously
canceled before taking the mutex.
Avoid a bug where we would indefinitely delay the connection loss
indication by re-queuing the connection loss work on consecutive beacon
loss events.

Cc: bartosz.markowski <bartosz.markowski@tieto.com>
Signed-off-by: Arik Nemtsov <arik@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>

...

This commit is contained in:

Arik Nemtsov 2012-05-15 17:08:54 +03:00 • committed by Luciano Coelho

parent 6e066921b3

commit 6b8bf5bc5e

2 changed files with 19 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

15

drivers/net/wireless/ti/wlcore/event.c

View file

10

drivers/net/wireless/ti/wlcore/main.c

View file