Linux bluetooth development
 help / color / mirror / Atom feed
From: "Frédéric Danis" <frederic.danis@collabora.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1] adapter: Fix crash on dev_disconnected
Date: Fri, 3 Jul 2026 09:14:55 +0200	[thread overview]
Message-ID: <e9c7f5a3-5ad6-49c4-9f29-4ba9bc07e059@collabora.com> (raw)
In-Reply-To: <20260702155037.9931-1-luiz.dentz@gmail.com>

Hi Luiz,

On 02/07/2026 17:50, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Commit 5d836f1c697c ("adapter: Fix failed bonding attempt after LE
> link disconnection") introduces a regression since it attempts to
> call device_is_connected after adapter_remove_connection which may
> free the device causing the following backtrace:
>
>      #0 0x5cd6e384262f in btd_device_bearer_is_connected src/device.c:3754
>      #1 0x5cd6e384266f in btd_device_is_connected src/device.c:3745
>      #2 0x5cd6e37f8614 in dev_disconnected src/adapter.c:8626
>
> Fixes: https://github.com/bluez/bluez/issues/2221
> ---
>   src/adapter.c | 25 +++++++++++++++++++++----
>   1 file changed, 21 insertions(+), 4 deletions(-)
>
> diff --git a/src/adapter.c b/src/adapter.c
> index 538f63e0a153..210225243f00 100644
> --- a/src/adapter.c
> +++ b/src/adapter.c
> @@ -7612,12 +7612,16 @@ struct agent *adapter_get_agent(struct btd_adapter *adapter)
>   static void adapter_remove_connection(struct btd_adapter *adapter,
>   						struct btd_device *device,
>   						uint8_t bdaddr_type,
> -						uint8_t reason)
> +						uint8_t reason,
> +						bool *removed)
>   {
>   	bool remove_device = false;
>   
>   	DBG("");
>   
> +	if (removed)
> +		*removed = false;
> +
>   	if (!g_slist_find(adapter->connections, device)) {
>   		btd_error(adapter->dev_id, "No matching connection for device");
>   		return;
> @@ -7638,6 +7642,9 @@ static void adapter_remove_connection(struct btd_adapter *adapter,
>   
>   		DBG("Removing temporary device %s", path);
>   		btd_adapter_remove_device(adapter, device);
> +
> +		if (removed)
> +			*removed = true;
>   	}
>   }
>   
> @@ -7665,10 +7672,10 @@ static void adapter_stop(struct btd_adapter *adapter)
>   		uint8_t addr_type = btd_device_get_bdaddr_type(device);
>   
>   		adapter_remove_connection(adapter, device, BDADDR_BREDR,
> -						MGMT_DEV_DISCONN_UNKNOWN);
> +						MGMT_DEV_DISCONN_UNKNOWN, NULL);
>   		if (addr_type != BDADDR_BREDR)
>   			adapter_remove_connection(adapter, device, addr_type,
> -						MGMT_DEV_DISCONN_UNKNOWN);
> +						MGMT_DEV_DISCONN_UNKNOWN, NULL);
>   	}
>   
>   	g_dbus_emit_property_changed(dbus_conn, adapter->path,
> @@ -8618,7 +8625,17 @@ static void dev_disconnected(struct btd_adapter *adapter,
>   
>   	device = btd_adapter_find_device(adapter, &addr->bdaddr, addr->type);
>   	if (device) {
> -		adapter_remove_connection(adapter, device, addr->type, reason);
> +		bool removed;
> +
> +		adapter_remove_connection(adapter, device, addr->type, reason,
> +						&removed);
> +		/* No need to continue if device was removed from the adapter,
> +		 * as it will be freed and the disconnect notify will be called
> +		 * in the device free callback.
> +		 */
> +		if (removed)
> +			return;
> +
>   		disconnect_notify(device, reason);
>   	}
>   

I tested this and crash is fixed.

Frédéric Danis

-- 
Frédéric Danis
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718



      parent reply	other threads:[~2026-07-03  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 15:50 [PATCH BlueZ v1] adapter: Fix crash on dev_disconnected Luiz Augusto von Dentz
2026-07-02 17:46 ` [BlueZ,v1] " bluez.test.bot
2026-07-03  7:14 ` Frédéric Danis [this message]

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=e9c7f5a3-5ad6-49c4-9f29-4ba9bc07e059@collabora.com \
    --to=frederic.danis@collabora.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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