The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Zhengping Jiang <jiangzp@google.com>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: qca: fix NULL-deref on non-serdev setup
Date: Mon, 22 Apr 2024 14:51:54 +0200	[thread overview]
Message-ID: <ZiZdag8fw8H1haCb@hovoldconsulting.com> (raw)
In-Reply-To: <20240319154611.2492-1-johan+linaro@kernel.org>

Hi Luiz,

On Tue, Mar 19, 2024 at 04:46:09PM +0100, Johan Hovold 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 address in pre-6.2 stable kernels.

> Johan Hovold (2):
>   Bluetooth: qca: fix NULL-deref on non-serdev suspend
>   Bluetooth: qca: fix NULL-deref on non-serdev setup

Could you pick these up for 6.9 or 6.10?

The patches are marked for stable backport and only privileged users can
set the N_HCI line discipline these days (even if I'm not sure about
pre-5.14 kernels...) so it may be fine to wait for 6.10 if you prefer.

Johan

  parent reply	other threads:[~2024-04-22 12:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 15:46 [PATCH 0/2] Bluetooth: qca: fix NULL-deref on non-serdev setup Johan Hovold
2024-03-19 15:46 ` [PATCH 1/2] Bluetooth: qca: fix NULL-deref on non-serdev suspend Johan Hovold
2024-03-19 15:46 ` [PATCH 2/2] Bluetooth: qca: fix NULL-deref on non-serdev setup Johan Hovold
2024-04-22 12:51 ` Johan Hovold [this message]
2024-04-22 13:04   ` [PATCH 0/2] " quic_zijuhu
2024-04-22 13:20     ` Johan Hovold
2024-04-22 13:30       ` quic_zijuhu
2024-04-22 13:43         ` Johan Hovold
2024-04-22 13:53           ` quic_zijuhu
2024-04-22 14:15             ` Luiz Augusto von Dentz
2024-04-22 14:22               ` quic_zijuhu
2024-04-22 15:02             ` Johan Hovold
2024-04-22 15:19               ` quic_zijuhu
2024-04-22 13:44       ` Luiz Augusto von Dentz
2024-04-22 13:51         ` Johan Hovold
2024-04-22 13:52           ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZiZdag8fw8H1haCb@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=jiangzp@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox