diff options
author | Jeffy Chen <jeffy.chen@rock-chips.com> | 2017-06-27 17:34:42 +0800 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2017-06-27 19:32:11 +0200 |
commit | 25717382c1dd0ddced2059053e3ca5088665f7a5 (patch) | |
tree | ffe5af4a8f3d9b254f0575dd57eae84a78f46fb7 /ipc/msgutil.c | |
parent | cdd24a200a8fa39e383890bbf862c0aa83ba83f5 (diff) |
Bluetooth: bnep: fix possible might sleep error in bnep_session
It looks like bnep_session 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>
Reviewed-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: AL Yu-Chen Cho <acho@suse.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'ipc/msgutil.c')
0 files changed, 0 insertions, 0 deletions