Skip to contentSkip to conversation

selinux: allow reading labels before policy is loaded

PATCH Superseded Jonathan Lebon 3 participants 3 messages May 27, 2020 SELinux security module

v2 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 selinux: allow reading labels before policy is loaded

This patch does for getxattr what 3e3e24b4204 did for setxattr; it allows querying the current SELinux label on disk before the policy is loaded.

One of the motivations described in that commit message also drives this
patch: for Fedora CoreOS (and eventually RHEL CoreOS), we want to be able to move the root filesystem for example, from xfs to ext4 on RAID, on first boot, at initrd time.[1]

Because such an operation works at the filesystem level, we need to be able to read the SELinux labels first from the original root, and apply them to the files of the new root. Commit 3e3e24b4204 enabled the second part of this process; this patch enables the first part.

[1] https://github.com/coreos/fedora-coreos-tracker/issues/94

---
 security/selinux/hooks.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
security/selinux/hooks.c +3 -1
index 0b4e32161b7..67ee2cfc25b 100644
@@ -3334,7 +3334,9 @@ static int selinux_inode_getsecurity(struct inode *inode, const char *name, void
 	char *context = NULL;
 	struct inode_security_struct *isec;
 
-	if (strcmp(name, XATTR_SELINUX_SUFFIX))
+	/* If we're not initialized yet, then we can't validate contexts,
+	 * so just let vfs_getxattr fall back to using the on-disk xattr. */
+	if (strcmp(name, XATTR_SELINUX_SUFFIX) || !selinux_state.initialized)
 		return -EOPNOTSUPP;
 
 	/*
Signature · 1 line
2.25.4
#1 lore raw
Quoted 26 lines · Jonathan Lebon

This patch does for getxattr what 3e3e24b4204 did for setxattr; it allows querying the current SELinux label on disk before the policy is loaded.

One of the motivations described in that commit message also drives this
patch: for Fedora CoreOS (and eventually RHEL CoreOS), we want to be able to move the root filesystem for example, from xfs to ext4 on RAID, on first boot, at initrd time.[1]

Because such an operation works at the filesystem level, we need to be able to read the SELinux labels first from the original root, and apply them to the files of the new root. Commit 3e3e24b4204 enabled the second part of this process; this patch enables the first part.

[1] https://github.com/coreos/fedora-coreos-tracker/issues/94

---
 security/selinux/hooks.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
security/selinux/hooks.c +0 -0
index 0b4e32161b7..67ee2cfc25b 100644

security/selinux/hooks.c static int selinux_inode_getsecurity(struct inode *inode, const char *name, void · line 3339

Quoted 7 lines
security/selinux/hooks.c +3 -1
@@ -3334,7 +3334,9 @@ static int selinux_inode_getsecurity(struct inode *inode, const char *name, void
        char *context = NULL;
        struct inode_security_struct *isec;
 
-       if (strcmp(name, XATTR_SELINUX_SUFFIX))
+       /* If we're not initialized yet, then we can't validate contexts,
+        * so just let vfs_getxattr fall back to using the on-disk xattr. */
+       if (strcmp(name, XATTR_SELINUX_SUFFIX) || !selinux_state.initialized)

Just two small notes:
1. We now have a helper for accessing selinux_state.initialized - selinux_initialized() - to ensure proper memory access ordering. Please use that instead of accessing it directly.
2. I'd suggest to make the new condition first in the || expression - it is cheaper than strcmp() so it could save some cycles during early boot.

Otherwise LGTM.

Quoted 6 lines
security/selinux/hooks.c +0 -1
                return -EOPNOTSUPP;
 
        /*
--

2.25.4

--
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel Red Hat, Inc.

maintainer
#2 lore raw
In reply to Jonathan Lebon
Quoted 2 lines · Jonathan Lebon

This patch does for getxattr what 3e3e24b4204 did for setxattr; it

Both above and down below you need to fix your commit reference to provide the one-line summary ala commit 3e3e24b42043 ("selinux: allow labeling before policy is loaded");
checkpatch.pl would have caught at least the 2nd instance for you. Probably could change
the 2nd reference to avoid need to repeat it.

Quoted 38 lines

allows querying the current SELinux label on disk before the policy is loaded.

One of the motivations described in that commit message also drives this
patch: for Fedora CoreOS (and eventually RHEL CoreOS), we want to be able to move the root filesystem for example, from xfs to ext4 on RAID, on first boot, at initrd time.[1]

Because such an operation works at the filesystem level, we need to be able to read the SELinux labels first from the original root, and apply them to the files of the new root. Commit 3e3e24b4204 enabled the second part of this process; this patch enables the first part.

[1] https://github.com/coreos/fedora-coreos-tracker/issues/94

---
 security/selinux/hooks.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
security/selinux/hooks.c +3 -2
index 0b4e32161b7..67ee2cfc25b 100644
@@ -3334,7 +3334,9 @@ static int selinux_inode_getsecurity(struct inode *inode, const char *name, void
        char *context = NULL;
        struct inode_security_struct *isec;
 
-       if (strcmp(name, XATTR_SELINUX_SUFFIX))
+       /* If we're not initialized yet, then we can't validate contexts,
+        * so just let vfs_getxattr fall back to using the on-disk xattr. */
+       if (strcmp(name, XATTR_SELINUX_SUFFIX) || !selinux_state.initialized)
                return -EOPNOTSUPP;
 
        /*
--

2.25.4