https://bugzilla.kernel.org/show_bug.cgi?id=202345 Bug ID: 202345 Summary: bluetoothd can end up with a corrupted DBus object path Product: Drivers Version: 2.5 Kernel Version: 4.9.130 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Bluetooth Assignee: linux-bluetooth@xxxxxxxxxxxxxxx Reporter: kai.ruhnau@xxxxxxxx Regression: No Three times during the past few days, I was able to end up with a bluetoothd daemon that reported a corrupted DBus object path (note the ']' character where '_' should be) # busctl tree org.bluez Failed to introspect object /org/bluez/hci0/dev_4F_D1_9D_30]B7_8D of service org.bluez: Invalid argument └─/org └─/org/bluez └─/org/bluez/hci0 […] GetManagedObjects works fine and reports the correct path: # busctl call org.bluez / org.freedesktop.DBus.ObjectManager GetManagedObjects […] "/org/bluez/hci0/dev_4F_D1_9D_30_B7_8D" 3 "org.freedesktop.DBus.Introspectable" 0 "org.bluez.Device1" 11 "Address" s "4F:D1:9D:30:B7:8D" "AddressType" s "random" "Alias" s "4F-D1-9D-30-B7-8D" "Paired" b false "Trusted" b false "Blocked" b false "LegacyPairing" b false "Connected" b false "UUIDs" as 0 "Adapter" o "/org/bluez/hci0" "ServicesResolved" b false "org.freedesktop.DBus.Properties" 0 […] Querying a property doesn't work, though: # busctl get-property org.bluez /org/bluez/hci0/dev_4F_D1_9D_30_B7_8D org.bluez.Device1 Address Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist And that last behavior then crashes my application. The most weird thing is that the object path corruption has been consistently at the fifth underscore (between the fourth and fifth address byte), but with different characters: a 'Y' (resulting in '/org/bluez/hci0/dev_xx_xx_xx_xxYxx_xx') , a '^', and today the above ']'. -- You are receiving this mail because: You are the assignee for the bug.
