diff options
| author | Jeffy Chen <jeffy.chen@rock-chips.com> | 2017-06-27 12:34:44 +0300 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2017-06-27 20:32:11 +0300 |
| commit | 5da8e47d849d3d37b14129f038782a095b9ad049 (patch) | |
| tree | c4a8dddef53c986f887653093cbf68516f633786 /drivers/bluetooth/hci_bcm.c | |
| parent | f06d977309d09253c744e54e75c5295ecc52b7b4 (diff) | |
| download | linux-5da8e47d849d3d37b14129f038782a095b9ad049.tar.xz | |
Bluetooth: hidp: fix possible might sleep error in hidp_session_thread
It looks like hidp_session_thread has same pattern as the issue reported in
old rfcomm:
while (1) {
set_current_state(TASK_INTERRUPTIBLE);
if (condition)
break;
// may call might_sleep here
schedule();
}
__set_current_state(TASK_RUNNING);
Which fixed at:
dfb2fae Bluetooth: Fix nested sleeps
So let's fix it at the same way, also follow the suggestion of:
https://lwn.net/Articles/628628/
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
Tested-by: AL Yu-Chen Cho <acho@suse.com>
Tested-by: Rohit Vaswani <rvaswani@nvidia.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/hci_bcm.c')
0 files changed, 0 insertions, 0 deletions