public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Sayers <kernel.org@pileofstuff.org>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, pav@iki.fi,
	Andrew Sayers <kernel.org@pileofstuff.org>
Subject: [PATCH BlueZ v5 1/6] pbap: Support calling pbap_init() after pbap_exit()
Date: Tue, 29 Apr 2025 15:14:11 +0100	[thread overview]
Message-ID: <20250429141533.803295-2-kernel.org@pileofstuff.org> (raw)
In-Reply-To: <20250429141533.803295-1-kernel.org@pileofstuff.org>

pbap_exit() didn't previously unregister itself thoroughly.  That
was fine if it was only called when the service was about to exit,
because everything was implicitly unregistered when the process ended.
But we need to be more scrupulous if this can be called throughout
the program's lifecycle.

Send the UnregisterProfile message directly from pbap_exit(),
then call unregister_profile().

The UnregisterProfile message can't be sent directly from
unregister_profile(), because that also needs to be called when
register_profile() fails halfway through.

Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
---
 obexd/client/pbap.c | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/obexd/client/pbap.c b/obexd/client/pbap.c
index 2f234fadf..90f8bdc02 100644
--- a/obexd/client/pbap.c
+++ b/obexd/client/pbap.c
@@ -1485,8 +1485,20 @@ void pbap_exit(void)
 {
 	DBG("");
 
-	dbus_connection_unref(conn);
-	conn = NULL;
+	g_dbus_remove_watch(system_conn, listener_id);
+
+	unregister_profile();
+
+	if (system_conn) {
+		dbus_connection_close(system_conn);
+		dbus_connection_unref(system_conn);
+		system_conn = NULL;
+	}
+
+	if (conn) {
+		dbus_connection_unref(conn);
+		conn = NULL;
+	}
 
 	obc_driver_unregister(&pbap);
 }
-- 
2.49.0


  reply	other threads:[~2025-04-29 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 14:14 [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive Andrew Sayers
2025-04-29 14:14 ` Andrew Sayers [this message]
2025-04-29 15:51   ` bluez.test.bot
2025-04-29 14:14 ` [PATCH BlueZ v5 2/6] obexd/bluetooth: Support calling bluetooth_init() after bluetooth_exit() Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 3/6] obexd: Support creating private system/session bus connections Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 4/6] obexd: Unregister profiles when the user is inactive Andrew Sayers
2025-04-29 17:25   ` Luiz Augusto von Dentz
2025-04-29 19:20     ` Andrew Sayers
2025-04-29 21:12       ` Luiz Augusto von Dentz
2025-04-29 14:14 ` [PATCH BlueZ v5 5/6] obexd: Support sd_login_monitor_get_timeout() Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 6/6] Revert "obexd: only run one instance at once" Andrew Sayers
2025-04-29 18:10 ` [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive patchwork-bot+bluetooth

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=20250429141533.803295-2-kernel.org@pileofstuff.org \
    --to=kernel.org@pileofstuff.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=pav@iki.fi \
    /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