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: Andrew Sayers <kernel.org@pileofstuff.org>
Subject: [PATCH v2 BlueZ 0/2] obexd: only run one instance at once
Date: Fri, 18 Apr 2025 16:30:50 +0100	[thread overview]
Message-ID: <20250418153115.1714964-1-kernel.org@pileofstuff.org> (raw)

Obex is a device-oriented protocol, so only one instance can run per device.
But Linux file security is user-oriented, so obexd should be a user service.
Tell systemd to only run this service for the first non-system user to log in.

This series causes systemd not to run obexd if it would just generate errors,
after adding a new bluez.tmpfiles file that distributors will need to install.

Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
---

V1 -> V2 add a hint in obex.service.in about installing the tmpfile
         (recommended by Luiz Augusto von Dentz)

Andrew Sayers (2):
      build: add bluez.tmpfiles
      obexd: only run one instance at once

 .gitignore                | 1 +
 configure.ac              | 1 +
 obexd/src/obex.service.in | 9 +++++++++
 tools/bluez.tmpfiles.in   | 1 +
 4 files changed, 12 insertions(+)


             reply	other threads:[~2025-04-18 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 15:30 Andrew Sayers [this message]
2025-04-18 15:30 ` [PATCH BlueZ v2 1/2] build: add bluez.tmpfiles Andrew Sayers
2025-04-18 15:35   ` Luiz Augusto von Dentz
2025-04-18 16:40     ` Andrew Sayers
2025-04-18 17:26       ` Pauli Virtanen
2025-04-18 18:09         ` Luiz Augusto von Dentz
2025-04-18 15:30 ` [PATCH BlueZ v2 2/2] obexd: only run one instance at once Andrew Sayers
2025-04-18 16:16 ` [PATCH v2 BlueZ 0/2] " Pauli Virtanen

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=20250418153115.1714964-1-kernel.org@pileofstuff.org \
    --to=kernel.org@pileofstuff.org \
    --cc=linux-bluetooth@vger.kernel.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