summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Moore <paul@paul-moore.com>2020-09-28 05:37:01 +0300
committerPaul Moore <paul@paul-moore.com>2020-09-29 23:50:57 +0300
commit0d50f059c4cdc9e436f6f4db8779ac0795bfdadf (patch)
tree748a4980a5adae0ce8c715747fc77061963b3f7f
parent8861d0af642c646c8e148ce34c294bdef6f32f6a (diff)
downloadlinux-0d50f059c4cdc9e436f6f4db8779ac0795bfdadf.tar.xz
selinux: provide a "no sooner than" date for the checkreqprot removal
We marked /sys/fs/selinux/checkreqprot as deprecated in Linux v5.7, but didn't provide any guidance as to the timeframe. Considering the state of checkreqprot, it seems like one year should be enough time. Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com> Signed-off-by: Paul Moore <paul@paul-moore.com>
-rw-r--r--Documentation/ABI/obsolete/sysfs-selinux-checkreqprot2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot b/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot
index 49ed9c8fd1e5..ed6b52ca210f 100644
--- a/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot
+++ b/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot
@@ -15,7 +15,7 @@ Description:
actual protection), and Android and Linux distributions have been
explicitly writing a "0" to /sys/fs/selinux/checkreqprot during
initialization for some time. Support for setting checkreqprot to 1
- will be removed in a future kernel release, at which point the kernel
+ will be removed no sooner than June 2021, at which point the kernel
will always cease using checkreqprot internally and will always
check the actual protections being applied upon mmap/mprotect calls.
The checkreqprot selinuxfs node will remain for backward compatibility