From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: [RFC PATCH] selinux: runtime disable is deprecated, add some ssleep() discomfort
Date: Tue, 02 Jun 2020 08:47:58 -0400 [thread overview]
Message-ID: <159110207843.57260.5661475689740939480.stgit@chester> (raw)
We deprecated the SELinux runtime disable functionality in Linux
v5.6, add a five second sleep to anyone using it to help draw their
attention to the deprecation.
Signed-off-by: Paul Moore <paul@paul-moore.com>
---
security/selinux/selinuxfs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/security/selinux/selinuxfs.c b/security/selinux/selinuxfs.c
index 4781314c2510..07af1334d9c9 100644
--- a/security/selinux/selinuxfs.c
+++ b/security/selinux/selinuxfs.c
@@ -30,6 +30,7 @@
#include <linux/uaccess.h>
#include <linux/kobject.h>
#include <linux/ctype.h>
+#include <linux/delay.h>
/* selinuxfs pseudo filesystem for exporting the security policy API.
Based on the proc code and the fs/nfsd/nfsctl.c code. */
@@ -287,6 +288,7 @@ static ssize_t sel_write_disable(struct file *file, const char __user *buf,
* kernel releases until eventually it is removed
*/
pr_err("SELinux: Runtime disable is deprecated, use selinux=0 on the kernel cmdline.\n");
+ ssleep(5);
if (count >= PAGE_SIZE)
return -ENOMEM;
next reply other threads:[~2020-06-02 12:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 12:47 Paul Moore [this message]
2020-06-02 12:49 ` [RFC PATCH] selinux: runtime disable is deprecated, add some ssleep() discomfort Paul Moore
2020-06-04 14:49 ` Stephen Smalley
2020-06-08 21:35 ` Paul Moore
2020-06-08 22:13 ` Stephen Smalley
2020-06-08 22:56 ` William Roberts
2020-06-10 14:03 ` Stephen Smalley
2020-06-10 14:11 ` Stephen Smalley
2020-06-11 13:29 ` Ondrej Mosnacek
2020-06-12 19:28 ` Paul Moore
2020-08-19 17:14 ` Petr Lautrbach
2020-08-19 19:07 ` Stephen Smalley
2020-08-19 19:16 ` Stephen Smalley
2020-08-20 15:41 ` Casey Schaufler
2020-08-20 16:58 ` Stephen Smalley
2020-08-20 20:31 ` Petr Lautrbach
2020-09-10 11:39 ` Ondrej Mosnacek
2020-09-10 12:33 ` Stephen Smalley
2020-09-23 18:32 ` Paul Moore
2020-09-24 23:42 ` Stephen Smalley
2020-09-10 13:31 ` Stephen Smalley
2020-09-10 14:36 ` Stephen Smalley
2020-09-10 14:54 ` Stephen Smalley
2020-06-12 19:00 ` Paul Moore
2020-06-12 18:56 ` Paul Moore
2022-03-01 22:53 Paul Moore
2022-03-01 22:57 ` Paul Moore
2022-03-01 23:02 ` Casey Schaufler
2022-04-04 20:23 ` 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=159110207843.57260.5661475689740939480.stgit@chester \
--to=paul@paul-moore.com \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).