linux/net/bluetooth, branch v4.0

Bluetooth: Fix potential NULL dereference

2015-02-03T08:02:12Z

The bnep_get_device function may be triggered by an ioctl just after a connection has gone down. In such a case the respective L2CAP chan->conn pointer will get set to NULL (by l2cap_chan_del). This patch adds a missing NULL check for this case in the bnep_get_device() function. Reported-by: Patrik Flykt Signed-off-by: Johan Hedberg Signed-off-by: Marcel Holtmann

Bluetooth: Remove mgmt_rp_read_local_oob_ext_data struct

2015-02-02T17:27:56Z

This extended return parameters struct conflicts with the new Read Local OOB Extended Data command definition. To avoid the conflict simply rename the old "extended" version to the normal one and update the code appropriately to take into account the two possible response PDU sizes. Signed-off-by: Johan Hedberg Signed-off-by: Marcel Holtmann

Bluetooth: Add restarting to service discovery

2015-02-02T07:52:34Z

When using LE_SCAN_FILTER_DUP_ENABLE, some controllers would send advertising report from each LE device only once. That means that we don't get any updates on RSSI value, and makes Service Discovery very slow. This patch adds restarting scan when in Service Discovery, and device with filtered uuid is found, but it's not in RSSI range to send event yet. This way if device moves into range, we will quickly get RSSI update. Signed-off-by: Jakub Pawlowski Signed-off-by: Marcel Holtmann

Bluetooth: Add le_scan_restart work for LE scan restarting

2015-02-02T07:52:33Z

Currently there is no way to restart le scan, and it's needed in service scan method. The way it work: it disable, and then enable le scan on controller. During the restart, we must remember when the scan was started, and it's duration, to later re-schedule the le_scan_disable work, that was stopped during the stop scan phase. Signed-off-by: Jakub Pawlowski Signed-off-by: Marcel Holtmann

Bluetooth: Fix OOB data present for BR/EDR Secure Connections Only mode

2015-02-01T09:52:54Z

When using Secure Connections Only mode, then only P-256 OOB data is valid and should be provided. In case userspace provides P-192 and P-256 OOB data, then the P-192 values will be set to zero. However the present value of the IO capability exchange still mentioned that both values would be available. Fix this by telling the controller clearly that only the P-256 OOB data is present. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Expose remote OOB information as debugfs entry

2015-02-01T07:15:21Z

For debugging purposes it is good to know which OOB data is actually currently loaded for each controller. So expose that list via debugfs. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Expose hardware error code as debugfs entry

2015-02-01T07:14:55Z

When the Hardware Error event is send by the controller, the Bluetooth core stores the error code. Expose it via debugfs so it can be retrieved later on. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Expose debug keys usage setting via debugfs

2015-02-01T07:14:19Z

To allow easier debugging when debug keys are generated, provide debugfs entry for checking the setting of debug keys usage. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Track changes from HCI Write Simple Pairing Debug Mode command

2015-02-01T07:13:23Z

When the HCI Write Simple Pairing Debug Mode command has been issued, the result needs to be tracked and stored. The hdev->ssp_debug_mode variable is already present, but was never updated when the mode in the controller was actually changed. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Expose Secure Simple Pairing debug mode setting in debugfs

2015-02-01T07:12:56Z

The value of the ssp_debug_mode should be accessible via debugfs to be able to determine if a BR/EDR controller generates debugs keys or not. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg