btusb bluetooth driver: wait for 'waker' work too before closing
authorLinus Torvalds <torvalds@linux-foundation.org>
Wed, 11 Nov 2009 21:32:29 +0000 (13:32 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 11 Nov 2009 21:32:29 +0000 (13:32 -0800)
commit404291ac9e72d118fcadeb939a69b2caa0a0e9ca
treee633e9d3f33b4a72ac3aea94a5868dda2828375d
parentfd801452a30927ec0dff84e541191e611c1afd0c
btusb bluetooth driver: wait for 'waker' work too before closing

Rafael debugged a resume-time hang (with oopses in workqueue handling)
on his laptop that was due to the 'waker' workqueue entry being
disconnected and then released without the workqueue entry having been
synchronized.

Several people were involved, with Oleg Nesterov doing a debugging patch
showing what workqueue entry was corrupt etc.

This was a regression introduced by commit 7bee549e19 ("Bluetooth: Add
USB autosuspend support to btusb driver") as Rafael points out (not
actually bisected, but it became clear once the bug was found).

Tested-and-reported-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Oliver Neukum <oliver@neukum.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
drivers/bluetooth/btusb.c