Hi Johan, > When we're doing background scanning and connection attempts it's > possible we timeout trying to connect and go back to scanning again. > The timeout triggers a HCI_LE_Create_Connection_Cancel which will > trigger a Connection Complete with "Unknown Connection Identifier" > error status. Since we go back to scanning this isn't really a failure > and shouldn't be presented as such to user space through mgmt. > > The exception to this is if the connection attempt was due to an > explicit request on an L2CAP socket (indicated by > params->explicit_connect being true). Since the socket will get an > error it's consistent to also notify the failure on mgmt in this case. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > net/bluetooth/hci_conn.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
