Message ID | 20230720190201.446469-1-luiz.dentz@gmail.com (mailing list archive) |
---|---|
State | Handled Elsewhere |
Headers | show |
Series | pull-request: bluetooth 2023-07-20 | expand |
On Thu, 20 Jul 2023 12:02:00 -0700 Luiz Augusto von Dentz wrote: > bluetooth pull request for net: > > - Fix building with coredump disabled > - Fix use-after-free in hci_remove_adv_monitor > - Use RCU for hci_conn_params and iterate safely in hci_sync > - Fix locking issues on ISO and SCO > - Fix bluetooth on Intel Macbook 2014 One bad fixes tag here, but good enough. Hopefully the big RCU-ifying patch won't blow up :)
Hi Jakub, On Thu, Jul 20, 2023 at 2:25 PM Jakub Kicinski <kuba@kernel.org> wrote: > > On Thu, 20 Jul 2023 12:02:00 -0700 Luiz Augusto von Dentz wrote: > > bluetooth pull request for net: > > > > - Fix building with coredump disabled > > - Fix use-after-free in hci_remove_adv_monitor > > - Use RCU for hci_conn_params and iterate safely in hci_sync > > - Fix locking issues on ISO and SCO > > - Fix bluetooth on Intel Macbook 2014 > > One bad fixes tag here, but good enough. > Hopefully the big RCU-ifying patch won't blow up :) Weird, I'd run verify-fixes and it didn't show up anything. As for the RCU changes, yeah I was considering pulling it out but since it is a single commit with no other dependencies we can always just revert it if it causes problems.
Hello: This pull request was applied to netdev/net.git (main) by Jakub Kicinski <kuba@kernel.org>: On Thu, 20 Jul 2023 12:02:00 -0700 you wrote: > The following changes since commit ac528649f7c63bc233cc0d33cff11f767cc666e3: > > Merge branch 'net-support-stp-on-bridge-in-non-root-netns' (2023-07-20 10:46:33 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2023-07-20 > > [...] Here is the summary with links: - pull-request: bluetooth 2023-07-20 https://git.kernel.org/netdev/net/c/75d42b351f56 You are awesome, thank you!
On Thu, 20 Jul 2023 14:30:02 -0700 Luiz Augusto von Dentz wrote: > > One bad fixes tag here, but good enough. > > Hopefully the big RCU-ifying patch won't blow up :) > > Weird, I'd run verify-fixes and it didn't show up anything. I think it works by checking the git database. If the commit exists in your git it will not complain. So you need a somewhat pristine repo instance to avoid false negatives.