From: Lennart Poettering <lennart@poettering.net>
Date: Fri, 7 Mar 2025 09:37:54 +0000 (+0100)
Subject: pid1: lower log level if BPF LSM is not available
X-Git-Tag: v258-rc1~1152
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=60cc2d54e035581dac2f425a6851352122224c17;p=thirdparty%2Fsystemd.git

pid1: lower log level if BPF LSM is not available

Currently, if you boot PID 1 in a container you always see a complaint
that BPF LSM won't work. That's fine, and log worthy, but probably not
above debug level. After all this is a really common case, and we should
gracefully adopt to our execution environment.
---

diff --git a/src/core/bpf-restrict-fs.c b/src/core/bpf-restrict-fs.c
index c6c6dffed4e..3f2ea2b9e6c 100644
--- a/src/core/bpf-restrict-fs.c
+++ b/src/core/bpf-restrict-fs.c
@@ -107,7 +107,7 @@ bool bpf_restrict_fs_supported(bool initialize) {
 
         r = lsm_supported("bpf");
         if (r == -ENOPKG) {
-                log_info_errno(r, "bpf-restrict-fs: securityfs not mounted, BPF LSM support not available.");
+                log_debug_errno(r, "bpf-restrict-fs: securityfs not mounted, BPF LSM support not available.");
                 return (supported = false);
         }
         if (r < 0) {