https://bugzilla.kernel.org/show_bug.cgi?id=218651 Luiz Von Dentz (luiz.dentz@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luiz.dentz@xxxxxxxxx --- Comment #20 from Luiz Von Dentz (luiz.dentz@xxxxxxxxx) --- (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #14) > Fix now queued for the next release of all affected stable/longterm series Hmm, was the original change backported to stable kernels, afaik I didn't mark it to Cc stable: commit 63298d6e752fc0ec7f5093860af8bc9f047b30c8 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: Tue Jan 9 13:45:40 2024 -0500 Bluetooth: hci_core: Cancel request on command timeout If command has timed out call __hci_cmd_sync_cancel to notify the hci_req since it will inevitably cause a timeout. This also rework the code around __hci_cmd_sync_cancel since it was wrongly assuming it needs to cancel timer as well, but sometimes the timers have not been started or in fact they already had timed out in which case they don't need to be cancel yet again. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> I wonder why it got selected to be backported, in any case I don't think it is a good idea to attempt to do backporting without having at least a Fixes tag to begin with otherwise we risk having problems like this widespread to people not really running the latest where this sort of problem is sort of expected during the early rc phase, so instead of having these 2 patches backported we could just remove the above from the stable trees. -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
