From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 941dbc: device: Fix memory leak
Date: Thu, 19 Jun 2025 11:15:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f5fd7e-ab13c2@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 941dbc5f3b56fea087a3b88bc73cf2776c02d4d5
https://github.com/bluez/bluez/commit/941dbc5f3b56fea087a3b88bc73cf2776c02d4d5
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix memory leak
This frees the LastUsedBearer string to avoid memory leak:
Direct leak of 12 byte(s) in 2 object(s) allocated from:
#0 0x7ccf538fd9c7 in malloc ../../../../src/libsanitizer/asan/
asan_malloc_linux.cpp:69
#1 0x7ccf53665b09 in g_malloc (/lib/x86_64-linux-gnu/
libglib-2.0.so.0+0x62b09)
#2 0x7ccf53659b90 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x56b90)
#3 0x7ccf53659cd4 in g_key_file_get_string (/lib/x86_64-linux-gnu/
libglib-2.0.so.0+0x56cd4)
#4 0x5c8c691f2811 in load_info src/device.c:4225
Commit: b8bbd5236ee008e25148477fa6390006b6113e7f
https://github.com/bluez/bluez/commit/b8bbd5236ee008e25148477fa6390006b6113e7f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: Add -U/--usb option
This adds option to use a host controller plugged over USB:
> tools/test-runner -U "usb-host,vendorid=0x8087,productid=0x0036"... -- /bin/bash
> dmesg
[ 1.046214] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[ 1.192623] Bluetooth: hci0: Firmware timestamp 2025.18 buildtype 2 build 82364
[ 1.192638] Bluetooth: hci0: Firmware SHA1: 0xa66e016b
[ 1.197362] Bluetooth: hci0: Fseq status: Success (0x00)
[ 1.197368] Bluetooth: hci0: Fseq executed: 00.00.04.196
[ 1.197371] Bluetooth: hci0: Fseq BT Top: 00.00.04.197
> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0036 Intel Corp. BE200 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Commit: 6f67234aa71bf9cdc6d939fc7c01427c85b19034
https://github.com/bluez/bluez/commit/6f67234aa71bf9cdc6d939fc7c01427c85b19034
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M doc/test-runner.rst
Log Message:
-----------
test-runner.rst: Add documentation for USB-passthrough
This documents the newly added option -U/--usb and adds a dedicated
section that explains the required the kernel image to build with
some extra config options to enable passing -device qemu-xhci in order
to use -device usb-host.
Commit: ab13c24eab8759da1d0b696c76745329bc18cb95
https://github.com/bluez/bluez/commit/ab13c24eab8759da1d0b696c76745329bc18cb95
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M doc/tester.config
Log Message:
-----------
tester.config: Add config options for USB-passthrough and drivers
This adds the necessary options in order to enable USB-passthrough
configuration and also enable most of the drivers so they get
build-tested.
Compare: https://github.com/bluez/bluez/compare/f5fd7efee7c3...ab13c24eab87
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-19 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/master/f5fd7e-ab13c2@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox