All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bluez PATCH v3] adapter - Device needs to be in the temporary state after pairing failed
@ 2020-08-24 18:44 Yu Liu
  0 siblings, 0 replies; only message in thread
From: Yu Liu @ 2020-08-24 18:44 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: chromeos-bluetooth-upstreaming, Yu Liu, sonnysasaka

This caused the device hanging around as a discovered device forever
even if it is turned off or not in present.

Reviewed-by: sonnysasaka@chromium.org

---

Changes in v3:
- Fix comment format
- Don't set temporary for trusted device

Changes in v2:
- Fix title length and format issue

Changes in v1:
- Initial change

 src/device.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/device.c b/src/device.c
index bb8e07e8f..103b5df27 100644
--- a/src/device.c
+++ b/src/device.c
@@ -6008,6 +6008,14 @@ void device_bonding_complete(struct btd_device *device, uint8_t bdaddr_type,
 
 	if (status) {
 		device_cancel_authentication(device, TRUE);
+
+		/* Put the device back to the temporary state so that it will be
+		 * treated as a newly discovered device.
+		 */
+		if (!device_is_paired(device, bdaddr_type) &&
+				!device_is_trusted(device))
+			btd_device_set_temporary(device, true);
+
 		device_bonding_failed(device, status);
 		return;
 	}
-- 
2.28.0.297.g1956fa8f8d-goog


^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2020-08-24 18:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-24 18:44 [Bluez PATCH v3] adapter - Device needs to be in the temporary state after pairing failed Yu Liu

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.