diff options
| author | Jeffy Chen <jeffy.chen@rock-chips.com> | 2017-06-27 09:34:44 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-08-30 08:21:52 (GMT) |
| commit | 1b5fcb3b25f794957acbeec78800a18d4d0903b3 (patch) | |
| tree | 6187fc50ec566ff8954b8648e29b4240fb6eb314 /net/xfrm | |
| parent | 5f81b1f51b9cfcbfbe7a1abea09962c91bf485e7 (diff) | |
| download | linux-1b5fcb3b25f794957acbeec78800a18d4d0903b3.tar.xz | |
Bluetooth: hidp: fix possible might sleep error in hidp_session_thread
commit 5da8e47d849d3d37b14129f038782a095b9ad049 upstream.
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>
Cc: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/xfrm')
0 files changed, 0 insertions, 0 deletions