public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] adapter: Fix bt_uuid_hash() crash
Date: Thu, 22 Jan 2026 16:20:11 +0000	[thread overview]
Message-ID: <176909881109.1793166.2346543037511239157.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120163614.261494-1-frederic.danis@collabora.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 20 Jan 2026 17:36:14 +0100 you wrote:
> This is reproducible on Ubuntu 24.04, which enables libasan, by
> calling org.bluez.AdminPolicySet1.SetServiceAllowList() method with
> an array of UUIDs like ['110c','110e']:
> 
> bluetoothd[9975]: [:1.1435:method_call] > org.bluez.AdminPolicySet1.SetServiceAllowList [#468]
> bluetoothd[9975]: plugins/admin.c:set_service_allowlist() sender :1.1435
> =================================================================
> ==9975==ERROR: AddressSanitizer: unknown-crash on address 0x763aef383ee4 at pc 0x648113f85064 bp 0x7fffe4db4970 sp 0x7fffe4db4960
> WRITE of size 16 at 0x763aef383ee4 thread T0
>     #0 0x648113f85063 in bt_uuid16_to_uuid128 lib/bluetooth/uuid.c:35
>     #1 0x648113f85063 in bt_uuid_to_uuid128 lib/bluetooth/uuid.c:73
>     #2 0x648113e90459 in bt_uuid_hash src/adapter.c:3891
>     #3 0x763af2700a5b in g_hash_table_add (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x49a5b) (BuildId: 94bfd21331c311d3199726de93a2656d07c22b33)
>     #4 0x648113fa7232 in queue_foreach src/shared/queue.c:207
>     #5 0x648113eb69df in btd_adapter_set_allowed_uuids src/adapter.c:3924
>     #6 0x648113cd6f11 in service_allowlist_set plugins/admin.c:165
>     #7 0x648113cd8162 in set_service_allowlist plugins/admin.c:382
>     #8 0x648113f97564 in process_message gdbus/object.c:293
>     #9 0x763af2f6f553 in dbus_connection_dispatch (/lib/x86_64-linux-gnu/libdbus-1.so.3+0x18553) (BuildId: 47829078e4267099473c6cf5f5742f16ccb2644d)
>     #10 0x648113f86d47 in message_dispatch gdbus/mainloop.c:59
>     #11 0x763af271440d  (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5d40d) (BuildId: 94bfd21331c311d3199726de93a2656d07c22b33)
>     #12 0x763af2773766  (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0xbc766) (BuildId: 94bfd21331c311d3199726de93a2656d07c22b33)
>     #13 0x763af2714ef6 in g_main_loop_run (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5def6) (BuildId: 94bfd21331c311d3199726de93a2656d07c22b33)
>     #14 0x6481140bf9d8 in mainloop_run src/shared/mainloop-glib.c:65
>     #15 0x6481140c0306 in mainloop_run_with_signal src/shared/mainloop-notify.c:196
>     #16 0x648113c93d58 in main src/main.c:1550
>     #17 0x763af1a2a1c9 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58
>     #18 0x763af1a2a28a in __libc_start_main_impl ../csu/libc-start.c:360
>     #19 0x648113c96854 in _start (/home/fdanis/src/bluez/src/bluetoothd+0x65d854) (BuildId: 4e2b98c227059c308efb311ffe5b023d60e142ac)
> 
> [...]

Here is the summary with links:
  - [BlueZ] adapter: Fix bt_uuid_hash() crash
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fdf82c79f8f3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-22 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 16:36 [PATCH BlueZ] adapter: Fix bt_uuid_hash() crash Frédéric Danis
2026-01-20 17:40 ` [BlueZ] " bluez.test.bot
2026-01-22 16:20 ` patchwork-bot+bluetooth [this message]

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=176909881109.1793166.2346543037511239157.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --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