Marcel Holtmann 3d7a9d1c7e Bluetooth: Don't trigger disconnect timeout for security mode 3 pairing ... A remote device in security mode 3 that tries to connect will require the pairing during the connection setup phase. The disconnect timeout is now triggered within 10 milliseconds and causes the pairing to fail. If a connection is not fully established and a PIN code request is received, don't trigger the disconnect timeout. The either successful or failing connection complete event will make sure that the timeout is triggered at the right time. The biggest problem with security mode 3 is that many Bluetooth 2.0 device and before use a temporary security mode 3 for dedicated bonding. Based on a report by Johan Hedberg <johan.hedberg@nokia.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Tested-by: Johan Hedberg <johan.hedberg@nokia.com>		2009-05-09 18:09:52 -07:00
..
bnep
cmtp	Bluetooth: Remove some pointless conditionals before kfree_skb()	2009-02-27 06:14:49 +01:00
hidp
rfcomm	Bluetooth: Fix removing of RFCOMM DLC timer with DEFER_SETUP	2009-04-19 18:56:45 +02:00
af_bluetooth.c	Bluetooth: Fix poll() misbehavior when using BT_DEFER_SETUP	2009-02-27 06:14:46 +01:00
hci_conn.c	Bluetooth: Don't use hci_acl_connect_cancel() for incoming connections	2009-05-09 18:09:45 -07:00
hci_core.c	Bluetooth: Remove some pointless conditionals before kfree_skb()	2009-02-27 06:14:49 +01:00
hci_event.c	Bluetooth: Don't trigger disconnect timeout for security mode 3 pairing	2009-05-09 18:09:52 -07:00
hci_sock.c
hci_sysfs.c	Bluetooth: Fix wrong module refcount when connection setup fails	2009-05-09 18:09:38 -07:00
Kconfig
l2cap.c	Bluetooth: Remove some pointless conditionals before kfree_skb()	2009-02-27 06:14:49 +01:00
lib.c
Makefile
sco.c	Bluetooth: Ask upper layers for HCI disconnect reason	2009-02-27 06:14:43 +01:00