Qualcomm Bluetooth controllers can be registered either from a serdev
driver or from the Bluetooth line discipline. In the latter case, the
HCI UART serdev pointer is NULL, something which the driver needs to
handle without crashing.
This series fixes one such issue at setup() time which incidentally
masked a similar crash at suspend. Fix this in two separate patches so
that the latter issue is addressed in pre-6.2 stable kernels.
Johan
Johan Hovold (2):
Bluetooth: qca: fix NULL-deref on non-serdev suspend
Bluetooth: qca: fix NULL-deref on non-serdev setup
drivers/bluetooth/hci_qca.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--
2.43.2
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <[email protected]>:
On Mon, 22 Apr 2024 15:57:46 +0200 you wrote:
> Qualcomm Bluetooth controllers can be registered either from a serdev
> driver or from the Bluetooth line discipline. In the latter case, the
> HCI UART serdev pointer is NULL, something which the driver needs to
> handle without crashing.
>
> This series fixes one such issue at setup() time which incidentally
> masked a similar crash at suspend. Fix this in two separate patches so
> that the latter issue is addressed in pre-6.2 stable kernels.
>
> [...]
Here is the summary with links:
- [RESEND,1/2] Bluetooth: qca: fix NULL-deref on non-serdev suspend
https://git.kernel.org/bluetooth/bluetooth-next/c/8185331e953d
- [RESEND,2/2] Bluetooth: qca: fix NULL-deref on non-serdev setup
https://git.kernel.org/bluetooth/bluetooth-next/c/9201f29be2c9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html