profile: Fix remotely initiated connections without service Remotely initiated connections need to be associated to a service instance to avoid the following crash as reported by Vinicius Costa: bluetoothd[14366]: src/profile.c:ext_confirm() incoming connect from A0:4E:04:F6:F5:05 bluetoothd[14366]: src/profile.c:ext_confirm() hfp_hf authorizing connection from A0:4E:04:F6:F5:05 bluetoothd[14366]: src/agent.c:agent_ref() 0x6a85e0: ref=2 bluetoothd[14366]: src/agent.c:agent_authorize_service() authorize service request was sent for /org/bluez/hci0/dev_A0_4E_04_F6_F5_05 bluetoothd[14366]: src/profile.c:ext_svc_complete() Services resolved for A0:4E:04:F6:F5:05 bluetoothd[14366]: src/profile.c:ext_svc_complete() Services resolved but still waiting for authorization bluetoothd[14366]: src/profile.c:ext_auth() A0:4E:04:F6:F5:05 authorized to connect to hfp_hf bluetoothd[14366]: src/agent.c:agent_unref() 0x6a85e0: ref=1 bluetoothd[14366]: src/profile.c:ext_connect() hfp_hf connected to A0:4E:04:F6:F5:05 Program received signal SIGSEGV, Segmentation fault. btd_service_connecting_complete (service=0x0, err=err@entry=0) at src/service.c:315 315 if (service->state != BTD_SERVICE_STATE_DISCONNECTED &&

Diffstat

1 files changed, 8 insertions(+), 1 deletions(-)