Hi Jiri,
>>> 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/
>
> ...
>
>> all 3 patches have been applied to bluetooth-next tree.
>
> Hi,
>
> given users are hitting it in at least 4.4 and 4.12, can we have all
> three in all stables where this applies?
>
> 5da8e47d849d Bluetooth: hidp: fix possible might sleep error in
> hidp_session_thread
> f06d977309d0 Bluetooth: cmtp: fix possible might sleep error in cmtp_session
> 25717382c1dd Bluetooth: bnep: fix possible might sleep error in bnep_session
>
> I am not sure: to stable directly or via net stable?
as Dave said, just email -stable directly and have Greg pick them up.
Regards
Marcel
