summaryrefslogtreecommitdiffstats
path: root/block/kyber-iosched.c
diff options
context:
space:
mode:
authorJeffy Chen <jeffy.chen@rock-chips.com>2017-06-27 11:34:44 +0200
committerMarcel Holtmann <marcel@holtmann.org>2017-06-27 19:32:11 +0200
commit5da8e47d849d3d37b14129f038782a095b9ad049 (patch)
treec4a8dddef53c986f887653093cbf68516f633786 /block/kyber-iosched.c
parentBluetooth: cmtp: fix possible might sleep error in cmtp_session (diff)
downloadlinux-5da8e47d849d3d37b14129f038782a095b9ad049.tar.xz
linux-5da8e47d849d3d37b14129f038782a095b9ad049.zip
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 'block/kyber-iosched.c')
0 files changed, 0 insertions, 0 deletions