bluetooth.service: Fix ConfigurationDirectory warning
When running "systemctl start bluetooth.service" on some systems, this
error would appear:
systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
ConfigurationDirectoryMode was mistakenly thought to help sandbox the daemon, but the service configuration already sets ProtectSystem=strict but "If [ProtectSystem is] set to "strict" the entire file system hierarchy is mounted read-only", so bluetoothd can't write to /etc/bluetooth anyway.
--- src/bluetooth.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
src/bluetooth.service.in +1 -1
@@ -22,7 +22,7 @@ ProtectControlGroups=true StateDirectory=bluetooth StateDirectoryMode=0700 ConfigurationDirectory=bluetooth -ConfigurationDirectoryMode=0555 +ConfigurationDirectoryMode=0755 # Execute Mappings MemoryDenyWriteExecute=true
Signature · 1 line
2.55.0
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1148981
---Test result---
Test Summary:
CheckPatch FAIL 0.35 seconds GitLint FAIL 0.23 seconds BuildEll PASS 13.40 seconds BluezMake PASS 486.30 seconds CheckSmatch PASS 175.43 seconds bluezmakeextell PASS 61.93 seconds IncrementalBuild PASS 467.76 seconds ScanBuild PASS 546.90 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] bluetooth.service: Fix ConfigurationDirectory warning
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#52:
systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
/github/workspace/src/patch/14758855.patch total: 0 errors, 1 warnings, 8 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14758855.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] bluetooth.service: Fix ConfigurationDirectory warning
5: B1 Line exceeds max length (142>80): "systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)"
https://github.com/bluez/bluez/pull/2417
---
Regards,
Linux Bluetooth
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1148981/
---Test result---
Test Summary:
CheckPatch FAIL 0.43 seconds GitLint FAIL 0.33 seconds BuildEll PASS 20.42 seconds BluezMake PASS 389.23 seconds CheckSmatch PASS 297.73 seconds bluezmakeextell PASS 94.12 seconds IncrementalBuild PASS 376.80 seconds ScanBuild PASS 1131.09 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] bluetooth.service: Fix ConfigurationDirectory warning
WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#52:
systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
/github/workspace/src/patch/14758855.patch total: 0 errors, 1 warnings, 8 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14758855.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] bluetooth.service: Fix ConfigurationDirectory warning
5: B1 Line exceeds max length (142>80): "systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)"
https://github.com/bluez/bluez/pull/2511
---
Regards,
Linux Bluetooth
This patch was applied to bluetooth/bluez.git (master) by Luiz Augusto von Dentz <[email protected]>:
Hello:
This patch was applied to bluetooth/bluez.git (master) by Luiz Augusto von Dentz <[email protected]>:
Quoted 11 lines · On Thu, 20 Aug 2026 11:44:46 +0200 you wrote:
When running "systemctl start bluetooth.service" on some systems, this
error would appear:
systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)ConfigurationDirectoryMode was mistakenly thought to help sandbox the daemon, but the service configuration already sets ProtectSystem=strict but "If [ProtectSystem is] set to "strict" the entire file system hierarchy is mounted read-only", so bluetoothd can't write to
/etc/bluetoothanyway.[...]
Here is the summary with links:
- [BlueZ] bluetooth.service: Fix ConfigurationDirectory warning
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a79a955d4a8a
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html