All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: Re: [PATCH] selinux: provide a "no sooner than" date for the checkreqprot removal
Date: Tue, 29 Sep 2020 16:58:13 -0400	[thread overview]
Message-ID: <CAHC9VhTXEWDeYnx0XWmso=wEw0L-dPLbRLw-fESqMyf=iM91-Q@mail.gmail.com> (raw)
In-Reply-To: <160126062161.7010.15501362260483844999.stgit@sifl>

On Sun, Sep 27, 2020 at 10:37 PM Paul Moore <paul@paul-moore.com> wrote:
>
> 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.
>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
>  .../ABI/obsolete/sysfs-selinux-checkreqprot        |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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

As this is a minor documentation change and not anything more
significant I've gone ahead and merged this into selinux/next.

-- 
paul moore
www.paul-moore.com

      parent reply	other threads:[~2020-09-29 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  2:37 [PATCH] selinux: provide a "no sooner than" date for the checkreqprot removal Paul Moore
2020-09-28 13:43 ` Stephen Smalley
2020-09-29 20:58 ` Paul Moore [this message]

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='CAHC9VhTXEWDeYnx0XWmso=wEw0L-dPLbRLw-fESqMyf=iM91-Q@mail.gmail.com' \
    --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 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.