Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: f93a73b2a54c8b742f601bd3e15b6fb8407e4f44 https://github.com/bluez/bluez/commit/f93a73b2a54c8b742f601bd3e15b6fb8407e4f44 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2024-10-24 (Thu, 24 Oct 2024) Changed paths: M src/shared/bap.c Log Message: ----------- shared/bap: Fix crash on bt_bap_stream_disable Calls to bt_bap_stream_disable with unicast stream shall result in stream_disable if when acting as a server (!stream->client) otherwise it may lead to the following trace: bluetoothd[104990]: src/shared/bap.c:bap_queue_req() req 0x555555732470 (op 0x05) queue 0x55555571e850 bluetoothd[104990]: src/gatt-database.c:send_notification_to_device() GATT server sending notification bluetoothd[104990]: src/shared/bap.c:stream_notify_state() stream 0x55555571b7f0 bluetoothd[104990]: src/shared/bap.c:stream_notify_qos() stream 0x55555571b7f0 bluetoothd[104990]: src/gatt-database.c:send_notification_to_device() GATT server sending notification bluetoothd[104990]: src/shared/bap.c:bap_process_queue() bluetoothd[104990]: src/shared/bap.c:bap_send() req 0x555555732470 len 3 Program received signal SIGSEGV, Segmentation fault. bap_send (bap=bap@entry=0x555555730c50, req=req@entry=0x555555732470) at src/shared/bap.c:1490 Fixes: https://github.com/bluez/bluez/issues/991 Commit: d35bae15152bb61008f4ca5643184377ef31c7ff https://github.com/bluez/bluez/commit/d35bae15152bb61008f4ca5643184377ef31c7ff Author: Amisha Jain <quic_amisjain@xxxxxxxxxxx> Date: 2024-10-24 (Thu, 24 Oct 2024) Changed paths: M gobex/gobex.c Log Message: ----------- obex: Resolve SRM issue for PTS testcases Add check for unknown/undefined srm value. This fix is required to pass the below the PTS testcases : 1. OPP/SR/GOEP/SRM/BI-02-C 2. FTP/SR/GOEP/SRM/BI-02-C 3. PBAP/PSE/GOEP/SRM/BI-05-C Description - Verify that the Server ignores a SRM header with an invalid value in the PUT/GET request and carries on with the PUT/GET operation with SRM disabled. Current Behaviour - Server is sending SRM enable in the response even though receiving the unknown SRM value. To fix this, I have added the check to verify the valid SRM values before continuing with SRM enable. Compare: https://github.com/bluez/bluez/compare/ba98be035621...d35bae15152b To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
