Maksim Yevmenkin 82e1becc5f Fix dangling callout problem in the Bluetooth L2CAP code that leads to ... panic. The panic happens when outgoing L2CAP connection descriptor is deleted with the L2CAP command(s) pending in the queue. In this case when the last L2CAP command is deleted (due to cleanup) and reference counter for the L2CAP connection goes down to zero the auto disconnect timeout is incorrectly set. pjd gets credit for tracking this down and committing bandaid. Reported by: Jonatan B <onatan at gmail dot com> MFC after: 3 days		2005-08-31 18:13:23 +00:00
..
ng_bluetooth.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_bt3c.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_btsocket_hci_raw.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_btsocket_l2cap.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_btsocket_rfcomm.h	Make default RFCOMM session MTU match default L2CAP MTU.	2005-01-11 01:39:53 +00:00
ng_btsocket.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_h4.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_hci.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
ng_l2cap.h	Fix dangling callout problem in the Bluetooth L2CAP code that leads to	2005-08-31 18:13:23 +00:00
ng_ubt.h	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00