diff options
| author | Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com> | 2019-12-17 15:54:42 +0100 |
|---|---|---|
| committer | Brian Gix <brian.gix@intel.com> | 2019-12-18 07:46:16 -0800 |
| commit | b9a4d9410b0ea2b7c571820baa90743cbe92b78d (patch) | |
| tree | 776e1d5390908d3aef8583deed18921738f49abe /TODO | |
| parent | 4a1bea28b15b4ab9b9c962597162cb4070587763 (diff) | |
| download | bluez-b9a4d9410b0ea2b7c571820baa90743cbe92b78d.tar.gz | |
mesh: Fix getting managed objects from ObjectManager
D-Bus spec mandates that GetManagedObjects method of
org.freedesktop.DBus.ObjectManager interface returns *children* only:
https://dbus.freedesktop.org/doc/dbus-specification.html
> All returned object paths are children of the object path implementing
> this interface, i.e. their object paths start with the ObjectManager's
> object path plus '/'
Both test scripts and ELL abuse this by returning application interfaces
via ObjectManager attached to the same path, but other D-Bus
implementations do not, making Attach() fail because mandatory
interfaces cannot be found.
This patch fixes the issue by scanning hierarchy returned by
GetManagedObjects for object implementing org.bluez.mesh.Application1
interface and keeping that as node's app_path.
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions