[BLUETOOTH] rfcomm_worker(): fix wakeup race

Set TASK_INTERRUPTIBLE prior to testing the flag to avoid missed wakeups.

Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 2 insertions, 2 deletions

diff --git a/net/bluetooth/rfcomm/core.c b/net/bluetooth/rfcomm/core.c
index 10cc13cfae6c..fe7df90eb707 100644
--- a/net/bluetooth/rfcomm/core.c
+++ b/net/bluetooth/rfcomm/core.c
@@ -1851,18 +1851,18 @@ static void rfcomm_worker(void)
         BT_DBG("");
 
         while (!atomic_read(&terminate)) {
+                set_current_state(TASK_INTERRUPTIBLE);
                 if (!test_bit(RFCOMM_SCHED_WAKEUP, &rfcomm_event)) {
                         /* No pending events. Let's sleep.
                          * Incoming connections and data will wake us up. */
-                        set_current_state(TASK_INTERRUPTIBLE);
                         schedule();
                 }
+                set_current_state(TASK_RUNNING);
 
                 /* Process stuff */
                 clear_bit(RFCOMM_SCHED_WAKEUP, &rfcomm_event);
                 rfcomm_process_sessions();
         }
-        set_current_state(TASK_RUNNING);
         return;
 }