linux-next: duplicate patches in the bluetooth tree
From: Stephen Rothwell <hidden>
Date: 2025-06-10 02:26:48
Also in:
linux-next, lkml
Attachments
- (unnamed) [application/pgp-signature] 488 bytes
From: Stephen Rothwell <hidden>
Date: 2025-06-10 02:26:48
Also in:
linux-next, lkml
Hi all,
The following commits are also in the net tree as different commits
(but the same patches):
3812bd9eae38 ("Bluetooth: MGMT: Protect mgmt_pending list with its own lock")
fa2c8bfe6794 ("Bluetooth: btintel_pcie: Reduce driver buffer posting to prevent race condition")
e849b59c9db0 ("Bluetooth: btintel_pcie: Increase the tx and rx descriptor count")
31b3d39c89f9 ("Bluetooth: btintel_pcie: Fix driver not posting maximum rx buffers")
6c5d0010e8a4 ("Bluetooth: hci_core: fix list_for_each_entry_rcu usage")
These are commits
6fe26f694c82 ("Bluetooth: MGMT: Protect mgmt_pending list with its own lock")
bf2ffc4d14db ("Bluetooth: btintel_pcie: Reduce driver buffer posting to prevent race condition")
2dd711102ce6 ("Bluetooth: btintel_pcie: Increase the tx and rx descriptor count")
daabd2769850 ("Bluetooth: btintel_pcie: Fix driver not posting maximum rx buffers")
308a3a8ce8ea ("Bluetooth: hci_core: fix list_for_each_entry_rcu usage")
In the net tree.
Also commit
a214e21449f2 ("Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete")
is almost identical to commit
e6ed54e86aae ("Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete")
in the net tree and, due to other changes in the bluetooth tree, is
causing a conflict.
--
Cheers,
Stephen Rothwell