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 v2 3/5] obexd: Support creating private system/session bus connections
Date: Fri, 25 Apr 2025 18:13:02 +0100 [thread overview]
Message-ID: <20250425171505.573271-4-kernel.org@pileofstuff.org> (raw)
In-Reply-To: <20250425171505.573271-1-kernel.org@pileofstuff.org>
Obexd can either connect to the system or session bus.
We mostly share a common connection to that bus, but it can be useful
to have a private connection. For example, this allows us to quickly
unregister profiles when switching user.
Add obex_setup_dbus_connection_private(), which creates a new
connection to whichever bus was specified by the user.
Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
---
obexd/src/main.c | 8 ++++++++
obexd/src/obexd.h | 2 ++
2 files changed, 10 insertions(+)
diff --git a/obexd/src/main.c b/obexd/src/main.c
index 703173662..ca95a70de 100644
--- a/obexd/src/main.c
+++ b/obexd/src/main.c
@@ -253,6 +253,14 @@ DBusConnection *obex_setup_dbus_connection(const char *name,
return connection;
}
+DBusConnection *obex_setup_dbus_connection_private(const char *name,
+ DBusError *error)
+{
+ return g_dbus_setup_private(option_system_bus ?
+ DBUS_BUS_SYSTEM : DBUS_BUS_SESSION,
+ name, error);
+}
+
int main(int argc, char *argv[])
{
GOptionContext *context;
diff --git a/obexd/src/obexd.h b/obexd/src/obexd.h
index 5e5edc4de..560db29ce 100644
--- a/obexd/src/obexd.h
+++ b/obexd/src/obexd.h
@@ -33,3 +33,5 @@ const char *obex_option_capability(void);
DBusConnection *obex_get_dbus_connection(void);
DBusConnection *obex_setup_dbus_connection(const char *name,
DBusError *error);
+DBusConnection *obex_setup_dbus_connection_private(const char *name,
+ DBusError *error);
--
2.49.0
next prev parent reply other threads:[~2025-04-25 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 17:12 [PATCH BlueZ v2 0/4] obexd: unregister profiles when the user is inactive Andrew Sayers
2025-04-25 17:13 ` [PATCH BlueZ v2 1/5] pbap: Support calling pbap_init() after pbap_exit() Andrew Sayers
2025-04-25 18:50 ` obexd: unregister profiles when the user is inactive bluez.test.bot
2025-04-25 17:13 ` [PATCH BlueZ v2 2/5] obexd/bluetooth: Support calling bluetooth_init() after bluetooth_exit() Andrew Sayers
2025-04-25 17:13 ` Andrew Sayers [this message]
2025-04-25 17:13 ` [PATCH BlueZ v2 4/5] obexd: Unregister profiles when the user is inactive Andrew Sayers
2025-04-25 17:13 ` [PATCH BlueZ v2 5/5] Revert "obexd: only run one instance at once" Andrew Sayers
2025-04-25 18:20 ` [PATCH BlueZ v2 0/4] obexd: unregister profiles when the user is inactive 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=20250425171505.573271-4-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