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] avrcp: Fix crash on remote player changed
Date: Mon, 27 Jan 2025 15:10:31 +0000 [thread overview]
Message-ID: <173799063100.3128680.685095842597742889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250124110331.1003810-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 Fri, 24 Jan 2025 12:03:31 +0100 you wrote:
> bluetoothd crashes when the remote player changes while bluetoothd
> is waiting for avrcp_list_items reply.
>
> profiles/audio/player.c:1597:9: runtime error: member access within null pointer of type 'struct media_folder'
> AddressSanitizer:DEADLYSIGNAL
> =================================================================
> ==825871==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000020 (pc 0x602bb0fffabc bp 0x000000000020 sp 0x7ffef88216d0 T0)
> ==825871==The signal is caused by a READ memory access.
> ==825871==Hint: address points to the zero page.
> #0 0x602bb0fffabc in media_folder_find_item profiles/audio/player.c:1597
> #1 0x602bb100cd3b in media_folder_create_item profiles/audio/player.c:1877
> #2 0x602bb100cd3b in media_player_create_item profiles/audio/player.c:1928
> #3 0x602bb107eae6 in parse_media_element profiles/audio/avrcp.c:2605
> #4 0x602bb107eae6 in avrcp_list_items_rsp profiles/audio/avrcp.c:2706
> #5 0x602bb106892f in browsing_response profiles/audio/avctp.c:987
> #6 0x602bb106892f in session_browsing_cb profiles/audio/avctp.c:1028
> #7 0x73de85b1448d (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5d48d) (BuildId: 461eff2b4df472ba9c32b2358ae9ba018a59a8c5)
> #8 0x73de85b73716 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0xbc716) (BuildId: 461eff2b4df472ba9c32b2358ae9ba018a59a8c5)
> #9 0x73de85b14f76 in g_main_loop_run (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5df76) (BuildId: 461eff2b4df472ba9c32b2358ae9ba018a59a8c5)
> #10 0x602bb13a22a8 in mainloop_run src/shared/mainloop-glib.c:66
> #11 0x602bb13a2bb6 in mainloop_run_with_signal src/shared/mainloop-notify.c:189
> #12 0x602bb0fd0257 in main src/main.c:1544
> #13 0x73de84e2a1c9 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58
> #14 0x73de84e2a28a in __libc_start_main_impl ../csu/libc-start.c:360
> #15 0x602bb0fd3124 in _start (/home/fdanis/src/bluez/src/bluetoothd+0x5c8124) (BuildId: 367892bd0501d74713dd7341977abfac1b2c5d6a)
>
> [...]
Here is the summary with links:
- [BlueZ] avrcp: Fix crash on remote player changed
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fac78ca5dbbd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-27 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 11:03 [PATCH BlueZ] avrcp: Fix crash on remote player changed Frédéric Danis
2025-01-24 12:07 ` [BlueZ] " bluez.test.bot
2025-01-27 15:10 ` 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=173799063100.3128680.685095842597742889.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.