Hi Zumeng, > On 27 Nov 2018, at 14.22, Zumeng Chen <zumeng.chen@xxxxxxxxx> wrote: > There is a related kernel as shown in the below list > > https://bugzilla.kernel.org/show_bug.cgi?id=198699 > > I didn't think my patch is to fix this one because I think we need to sort out > the whole logic of CMD_COMPLETE. But my patch is good to fix the issue > described by subject. I’m still failing to see any major problem with command complete handling. This seems more related to sending HCI commands that do not complete in Command Complete (such as Inquiry or connection creation) through the hci_request framework together with hci_req_run_skb(). This could either happen by directly using the hci_req_sync() API, such as in the case of the legacy inquiry ioctl, or by some code using hci_cmd_sync() to send a command that does not complete in Command Complete. In these cases you end up with a Command Status with status == 0, which the hci_request code interprets as completion of the request, but is unable to fetch any return parameters from it (which for these cases is fine). Since what I've describe above is normal usage of the hci_req_sync() and hci_cmd_sync() APIs I still don’t see any other issue except that an error log was thrown rather than than (at most) a debug log. So I’d still go for the patch that I submitted earlier today. Johan
