From: Nikolay Borisov <nik.borisov@suse.com>
To: linux-security-module@vger.kernel.org
Cc: paul@paul-moore.com, serge@hallyn.com, kees@kernel.org,
linux-kernel@vger.kernel.org, kirill.shutemov@linux.intel.com,
linux-coco@lists.linux.dev,
Nikolay Borisov <nik.borisov@suse.com>
Subject: [PATCH 1/2] lockdown: Switch implementation to using bitmap
Date: Fri, 21 Mar 2025 12:24:20 +0200 [thread overview]
Message-ID: <20250321102422.640271-2-nik.borisov@suse.com> (raw)
In-Reply-To: <20250321102422.640271-1-nik.borisov@suse.com>
Tracking the lockdown at the depth granularity rather than at the
individual is somewhat inflexible as it provides an "all or nothing"
approach. Instead there are use cases where it will be useful to be
able to lockdown individual features - TDX for example wants to disable
access to just /dev/mem.
To accommodate this use case switch the internal implementation to using
a bitmap so that individual lockdown features can be turned on. At the
same time retain the existing semantic where
INTEGRITY_MAX/CONFIDENTIALITY_MAX are treated as wildcards meaning "lock
everything below me".
Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
---
security/lockdown/lockdown.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
index cf83afa1d879..5014d18c423f 100644
--- a/security/lockdown/lockdown.c
+++ b/security/lockdown/lockdown.c
@@ -10,12 +10,13 @@
* 2 of the Licence, or (at your option) any later version.
*/
+#include <linux/bitmap.h>
#include <linux/security.h>
#include <linux/export.h>
#include <linux/lsm_hooks.h>
#include <uapi/linux/lsm.h>
-static enum lockdown_reason kernel_locked_down;
+static DECLARE_BITMAP(kernel_locked_down, LOCKDOWN_CONFIDENTIALITY_MAX);
static const enum lockdown_reason lockdown_levels[] = {LOCKDOWN_NONE,
LOCKDOWN_INTEGRITY_MAX,
@@ -26,10 +27,15 @@ static const enum lockdown_reason lockdown_levels[] = {LOCKDOWN_NONE,
*/
static int lock_kernel_down(const char *where, enum lockdown_reason level)
{
- if (kernel_locked_down >= level)
- return -EPERM;
- kernel_locked_down = level;
+ if (level > LOCKDOWN_CONFIDENTIALITY_MAX)
+ return -EINVAL;
+
+ if (level == LOCKDOWN_INTEGRITY_MAX || level == LOCKDOWN_CONFIDENTIALITY_MAX)
+ bitmap_set(kernel_locked_down, 1, level);
+ else
+ bitmap_set(kernel_locked_down, level, 1);
+
pr_notice("Kernel is locked down from %s; see man kernel_lockdown.7\n",
where);
return 0;
@@ -62,13 +68,12 @@ static int lockdown_is_locked_down(enum lockdown_reason what)
"Invalid lockdown reason"))
return -EPERM;
- if (kernel_locked_down >= what) {
+ if (test_bit(what, kernel_locked_down)) {
if (lockdown_reasons[what])
pr_notice_ratelimited("Lockdown: %s: %s is restricted; see man kernel_lockdown.7\n",
current->comm, lockdown_reasons[what]);
return -EPERM;
}
-
return 0;
}
@@ -105,7 +110,7 @@ static ssize_t lockdown_read(struct file *filp, char __user *buf, size_t count,
if (lockdown_reasons[level]) {
const char *label = lockdown_reasons[level];
- if (kernel_locked_down == level)
+ if (test_bit(level, kernel_locked_down))
offset += sprintf(temp+offset, "[%s] ", label);
else
offset += sprintf(temp+offset, "%s ", label);
--
2.43.0
next prev parent reply other threads:[~2025-03-21 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 10:24 [PATCH 0/2] Allow individual features to be locked down Nikolay Borisov
2025-03-21 10:24 ` Nikolay Borisov [this message]
2025-03-21 20:34 ` [PATCH 1/2] lockdown: Switch implementation to using bitmap sergeh
2025-04-09 15:18 ` Nikolay Borisov
2025-03-21 10:24 ` [PATCH 2/2] lockdown/kunit: Introduce kunit tests Nikolay Borisov
2025-03-21 21:13 ` [PATCH 0/2] Allow individual features to be locked down Paul Moore
2025-04-09 15:45 ` Dan Williams
2025-04-09 15:47 ` Nikolay Borisov
2025-05-12 21:40 ` Dan Williams
2025-05-12 22:01 ` Paul Moore
2025-05-13 11:10 ` Nikolay Borisov
2025-05-13 23:07 ` Paul Moore
2025-04-13 19:25 ` Paul Moore
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=20250321102422.640271-2-nik.borisov@suse.com \
--to=nik.borisov@suse.com \
--cc=kees@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.