[PATCH BlueZ v1 0/2] client/cs: fix crash in reference ranging provider

[Naga Bhavani Akella <naga.akella@oss.qualcomm.com>]

`start <dev_addr> 30` followed by `register_provider /` segfaults
bluetoothctl on the first ProcedureData signal: cs_ranging_obj_create()
exported each device's RangingProvider1 object as a direct child of
"/", the one path with real gdbus object data (its ObjectManager), and
gdbus/object.c's invalidate_parent_data() dereferences a NULL parent
in that case.

Nest the exported objects under RANGING_PROVIDER_PATH
"/org/example/ranging") instead of "/" directly.
bluetoothd's provider watch matches any descendant
of the registered root, so discovery still works.

Patch 1 is the fix, patch 2 updates the docs to match.


Naga Bhavani Akella (2):
  client: avoid registering ranging objects as direct children of "/"
  doc: note RangingProvider1 objects are nested in bluetoothctl-cs

 client/cs.c             | 28 +++++++++++++++++++++++++++-
 doc/bluetoothctl-cs.rst |  8 +++++---
 2 files changed, 32 insertions(+), 4 deletions(-)

--