Bluetooth: Track LE initiator and responder address information

mirror of https://github.com/linux-apfs/linux-apfs.git synced 2026-05-01 15:00:59 -07:00

For SMP we need the local and remote addresses (and their types) that
were used to establish the connection. These may be different from the
Identity Addresses or even the current RPA. To guarantee that we have
this information available and it is correct track these values
separately from the very beginning of the connection.

For outgoing connections we set the values as soon as we get a
successful command status for HCI_LE_Create_Connection (for which the
patch adds a command status handler function) and for incoming
connections as soon as we get a LE Connection Complete HCI event.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

This commit is contained in:

Johan Hedberg

2014-02-28 12:54:16 +02:00

committed by

Marcel Holtmann

parent b46e003089

commit cb1d68f7a3

2 changed files with 82 additions and 0 deletions

									
										include/net/bluetooth/hci_core.h
									
		+4
		
												View File
												
				@@ -332,6 +332,10 @@ struct hci_conn {

					__u8		dst_type;

					bdaddr_t	src;

					__u8		src_type;

					bdaddr_t	init_addr;

					__u8		init_addr_type;

					bdaddr_t	resp_addr;

					__u8		resp_addr_type;

					__u16		handle;

					__u16		state;

					__u8		mode;