[PW_SID:1078304] [v2] Bluetooth: Add Broadcom channel priority commands by BluezTestBot · Pull Request #52 · bluez/bluetooth-next

BluezTestBot · 2026-04-09T19:45:09Z

From: Sasha Finkelstein fnkl.kernel@gmail.com

Certain Broadcom bluetooth chips (bcm4377/bcm4378/bcm438) need ACL
streams carrying audio to be set as "high priority" using a vendor
specific command to prevent 10-ish second-long dropouts whenever
something does a device scan. This patch sends the command when the
socket priority is set to TC_PRIO_INTERACTIVE, as BlueZ does for audio.

Signed-off-by: Sasha Finkelstein fnkl.kernel@gmail.com

Changes in v2:

new ioctl got nack-ed, so let's use sk_priority as the trigger
Link to v1: https://lore.kernel.org/r/20260407-brcm-prio-v1-1-f38b17376640@gmail.com

base-commit: bfe62a4
change-id: 20260407-brcm-prio-b630e6cc3834

Best regards,

bluez/action-ci uses master as default branch for workflow which is incorrect for kernel. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

Certain Broadcom bluetooth chips (bcm4377/bcm4378/bcm438) need ACL streams carrying audio to be set as "high priority" using a vendor specific command to prevent 10-ish second-long dropouts whenever something does a device scan. This patch sends the command when the socket priority is set to TC_PRIO_INTERACTIVE, as BlueZ does for audio. Signed-off-by: Sasha Finkelstein <fnkl.kernel@gmail.com>

github-actions · 2026-04-09T19:48:45Z

CheckPatch
Desc: Run checkpatch.pl script
Duration: 0.56 seconds
Result: PENDING

github-actions · 2026-04-09T19:48:46Z

GitLint
Desc: Run gitlint
Duration: 0.32 seconds
Result: PENDING

github-actions · 2026-04-09T19:48:46Z

SubjectPrefix
Desc: Check subject contains "Bluetooth" prefix
Duration: 0.08 seconds
Result: PASS

github-actions · 2026-04-09T19:49:16Z

BuildKernel
Desc: Build Kernel for Bluetooth
Duration: 24.31 seconds
Result: PASS

github-actions · 2026-04-09T19:49:47Z

CheckAllWarning
Desc: Run linux kernel with all warning enabled
Duration: 26.66 seconds
Result: PASS

github-actions · 2026-04-09T19:50:18Z

CheckSparse
Desc: Run sparse tool with linux kernel
Duration: 25.54 seconds
Result: PASS

github-actions · 2026-04-09T19:50:47Z

BuildKernel32
Desc: Build 32bit Kernel for Bluetooth
Duration: 24.24 seconds
Result: PASS

github-actions · 2026-04-09T19:59:23Z

TestRunnerSetup
Desc: Setup kernel and bluez for test-runner
Duration: 515.24 seconds
Result: PASS

github-actions · 2026-04-09T20:00:15Z

TestRunner_l2cap-tester
Desc: Run l2cap-tester with test-runner
Duration: 51.34 seconds
Result: FAIL
Output:

Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0

Failed Test Cases
L2CAP LE Client - Close socket 2                     Timed out   23.777 seconds

github-actions · 2026-04-09T20:00:55Z

TestRunner_iso-tester
Desc: Run iso-tester with test-runner
Duration: 38.77 seconds
Result: PASS

github-actions · 2026-04-09T20:01:02Z

TestRunner_bnep-tester
Desc: Run bnep-tester with test-runner
Duration: 6.30 seconds
Result: PASS

github-actions · 2026-04-09T20:02:53Z

TestRunner_mgmt-tester
Desc: Run mgmt-tester with test-runner
Duration: 110.50 seconds
Result: FAIL
Output:

Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.105 seconds

github-actions · 2026-04-09T20:03:04Z

TestRunner_rfcomm-tester
Desc: Run rfcomm-tester with test-runner
Duration: 9.32 seconds
Result: PASS

github-actions · 2026-04-09T20:03:21Z

TestRunner_sco-tester
Desc: Run sco-tester with test-runner
Duration: 16.39 seconds
Result: FAIL
Output:

WARNING: possible circular locking dependency detected
7.0.0-rc2-gaa582b6f213c #1 Not tainted
------------------------------------------------------
kworker/u5:2/117 is trying to acquire lock:
ffff8880025fe240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0

but task is already holding lock:
ffff888002141c20 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&conn->lock){+.+.}-{3:3}:
       lock_acquire+0xf7/0x2c0
       _raw_spin_lock+0x2a/0x40
       sco_sock_connect+0x4d7/0x1280
       __sys_connect+0x1a3/0x260
       __x64_sys_connect+0x6e/0xb0
       do_syscall_64+0xa0/0x570
       entry_SYSCALL_64_after_hwframe+0x74/0x7c

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
       check_prev_add+0xe9/0xc70
       __lock_acquire+0x1457/0x1df0
       lock_acquire+0xf7/0x2c0
       lock_sock_nested+0x36/0xd0
       sco_connect_cfm+0x358/0x8d0
       hci_sync_conn_complete_evt+0x3d3/0x8e0
       hci_event_packet+0x74f/0xb10
       hci_rx_work+0x398/0xd00
       process_scheduled_works+0xb16/0x1ac0
       worker_thread+0x4ff/0xba0
       kthread+0x368/0x490
       ret_from_fork+0x498/0x7e0
       ret_from_fork_asm+0x19/0x30

other info that might help us debug this:

...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-gaa582b6f213c #1 PREEMPT(lazy) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x49/0x60
 __might_resched+0x2ea/0x500
 lock_sock_nested+0x47/0xd0
 ? sco_connect_cfm+0x358/0x8d0
 sco_connect_cfm+0x358/0x8d0
 ? hci_debugfs_create_conn+0x190/0x210
 ? __pfx_sco_connect_cfm+0x10/0x10
 hci_sync_conn_complete_evt+0x3d3/0x8e0
 hci_event_packet+0x74f/0xb10
 ? __pfx_hci_sync_conn_complete_evt+0x10/0x10
 ? __pfx_hci_event_packet+0x10/0x10
 ? mark_held_locks+0x49/0x80
 ? lockdep_hardirqs_on_prepare+0xd4/0x180
 ? _raw_spin_unlock_irqrestore+0x2c/0x50
 hci_rx_work+0x398/0xd00
 process_scheduled_works+0xb16/0x1ac0
 ? __pfx_process_scheduled_works+0x10/0x10
 ? lock_acquire+0xf7/0x2c0
 ? lock_is_held_type+0x9b/0x110
 ? __pfx_hci_rx_work+0x10/0x10
 worker_thread+0x4ff/0xba0
 ? _raw_spin_unlock_irqrestore+0x2c/0x50
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x368/0x490
 ? _raw_spin_unlock_irq+0x23/0x40
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x498/0x7e0
 ? __pfx_ret_from_fork+0x10/0x10
 ? __switch_to+0x9e4/0xe50
 ? __switch_to_asm+0x32/0x60
...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 123, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 123 Comm: kworker/u5:2 Tainted: G        W           7.0.0-rc2-gaa582b6f213c #1 PREEMPT(lazy) 
Tainted: [W]=WARN
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x49/0x60
 __might_resched+0x2ea/0x500
 lock_sock_nested+0x47/0xd0
 ? sco_connect_cfm+0x358/0x8d0
 sco_connect_cfm+0x358/0x8d0
 ? hci_debugfs_create_conn+0x190/0x210
 ? __pfx_sco_connect_cfm+0x10/0x10
 hci_sync_conn_complete_evt+0x3d3/0x8e0
 hci_event_packet+0x74f/0xb10
 ? __pfx_hci_sync_conn_complete_evt+0x10/0x10
 ? __pfx_hci_event_packet+0x10/0x10
 ? percpu_rwsem_wait+0x390/0x400
 hci_rx_work+0x398/0xd00
 process_scheduled_works+0xb16/0x1ac0
 ? __schedule+0x7a0/0x1750
 ? __pfx_process_scheduled_works+0x10/0x10
 ? lock_release+0x39/0x260
 ? __pfx_hci_rx_work+0x10/0x10
 worker_thread+0x4ff/0xba0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x368/0x490
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x498/0x7e0
 ? __pfx_ret_from_fork+0x10/0x10
 ? __switch_to+0x9e4/0xe50
 ? __switch_to_asm+0x32/0x60
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x19/0x30
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0

github-actions · 2026-04-09T20:03:32Z

TestRunner_ioctl-tester
Desc: Run ioctl-tester with test-runner
Duration: 10.16 seconds
Result: PASS

github-actions · 2026-04-09T20:03:44Z

TestRunner_mesh-tester
Desc: Run mesh-tester with test-runner
Duration: 11.70 seconds
Result: FAIL
Output:

Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    1.977 seconds
Mesh - Send cancel - 2                               Timed out    1.990 seconds

github-actions · 2026-04-09T20:03:54Z

TestRunner_smp-tester
Desc: Run smp-tester with test-runner
Duration: 8.57 seconds
Result: PASS

github-actions · 2026-04-09T20:04:02Z

TestRunner_userchan-tester
Desc: Run userchan-tester with test-runner
Duration: 6.70 seconds
Result: PASS

github-actions · 2026-04-09T20:04:11Z

TestRunner_6lowpan-tester
Desc: Run 6lowpan-tester with test-runner
Duration: 8.62 seconds
Result: FAIL
Output:

WARNING: possible circular locking dependency detected
7.0.0-rc2-gaa582b6f213c #1 Not tainted
------------------------------------------------------
kworker/0:1/11 is trying to acquire lock:
ffff8880026e0940 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180

but task is already holding lock:
ffffffffbd84d720 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (rtnl_mutex){+.+.}-{4:4}:
       lock_acquire+0xf7/0x2c0
       __mutex_lock+0x16b/0x1fc0
       lowpan_register_netdev+0x11/0x30
       chan_ready_cb+0x836/0xd00
       l2cap_recv_frame+0x6a06/0x8920
       l2cap_recv_acldata+0x790/0xdf0
       hci_rx_work+0x500/0xd00
       process_scheduled_works+0xb16/0x1ac0
       worker_thread+0x4ff/0xba0
       kthread+0x368/0x490
       ret_from_fork+0x498/0x7e0
       ret_from_fork_asm+0x19/0x30

-> #3 (&chan->lock#3/1){+.+.}-{4:4}:
       lock_acquire+0xf7/0x2c0
       __mutex_lock+0x16b/0x1fc0
       l2cap_chan_connect+0x74e/0x1980
       lowpan_control_write+0x523/0x660
       full_proxy_write+0x10b/0x190
       vfs_write+0x1c0/0xf60
       ksys_write+0xf1/0x1d0
       do_syscall_64+0xa0/0x570
       entry_SYSCALL_64_after_hwframe+0x74/0x7c

-> #2 (&conn->lock){+.+.}-{4:4}:
...
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

github-actions · 2026-04-09T20:04:12Z

IncrementalBuild
Desc: Incremental build with the patches in the series
Duration: 0.36 seconds
Result: PENDING

Vudentz and others added 2 commits April 9, 2026 15:21

workflow/sync: Set workflow to use worflow branch

80f84c0

bluez/action-ci uses master as default branch for workflow which is incorrect for kernel. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

Vudentz force-pushed the workflow branch from 80f84c0 to 1cfbfee Compare April 9, 2026 19:46

Conversation

BluezTestBot commented Apr 9, 2026

Signed-off-by: Sasha Finkelstein fnkl.kernel@gmail.com

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants