Skip to content

RDKEMW-16417 : BtrCore_BTGetPairedDeviceInfo_8.3#68

Open
PreethiLakshmi91 wants to merge 1 commit intosupport/8.3.4.0from
feature/RDKEMW-16417
Open

RDKEMW-16417 : BtrCore_BTGetPairedDeviceInfo_8.3#68
PreethiLakshmi91 wants to merge 1 commit intosupport/8.3.4.0from
feature/RDKEMW-16417

Conversation

@PreethiLakshmi91
Copy link
Copy Markdown

Reason for change: Crash and memleak fix
Test Procedure: runbook test cases for bluetooth devices
Risks: Low
Priority: P1

Reason for change: Crash and memleak fix
Test Procedure: runbook test cases for bluetooth devices
Risks: Low
Priority: P1

Signed-off-by: ppalan289 <preethi_palanisamy@comcast.com>
@PreethiLakshmi91 PreethiLakshmi91 requested a review from a team as a code owner April 8, 2026 14:58
Copilot AI review requested due to automatic review settings April 8, 2026 14:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses a crash and potential leaks in the BlueZ5 DBus implementation of BtrCore_BTGetPairedDeviceInfo, improving robustness around DBus object enumeration and per-device property fetching.

Changes:

  • Added stronger NULL/connection validation before issuing DBus calls.
  • Fixed boolean property parsing type usage (dbus_bool_t) and added bounds checks when collecting paired device paths.
  • Improved cleanup on error paths by unref’ing DBus messages/replies consistently and validating dbus_message_append_args.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants