linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@vger.kernel.org, omosnace@redhat.com, corbet@lwn.net,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation,selinux: fix references to old selinuxfs mount point
Date: Tue, 7 Jan 2020 11:19:25 -0500	[thread overview]
Message-ID: <CAHC9VhQKZGa_g7Eq97WnUmzUAJDZoO5-sDhu1Qrxo7XRLjTPeA@mail.gmail.com> (raw)
In-Reply-To: <20200107154450.25961-1-sds@tycho.nsa.gov>

On Tue, Jan 7, 2020 at 10:44 AM Stephen Smalley <sds@tycho.nsa.gov> wrote:
> selinuxfs was originally mounted on /selinux, and various docs and
> kconfig help texts referred to nodes under it.  In Linux 3.0,
> /sys/fs/selinux was introduced as the preferred mount point for selinuxfs.
> Fix all the old references to /selinux/ to /sys/fs/selinux/.
>
> Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
> ---
>  Documentation/admin-guide/kernel-parameters.txt | 9 +++++----
>  security/selinux/Kconfig                        | 7 ++++---
>  2 files changed, 9 insertions(+), 7 deletions(-)

...

> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index ade4e6ec23e0..565d84760e48 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4349,8 +4350,8 @@
>                         0 -- disable.
>                         1 -- enable.
>                         Default value is set via kernel config option.
> -                       If enabled at boot time, /selinux/disable can be used
> -                       later to disable prior to initial policy load.
> +                       If enabled at boot time, /sys/fs/selinux/disable can
> +                       be used later to disable prior to initial policy load.

While we are modifying this, I would suggest adding a note about
/sys/fs/selinux/disable being deprecated, or simply remove mention of
/sys/fs/selinux/disable.  The latter option is probably the better
choice.

-- 
paul moore
www.paul-moore.com

  reply	other threads:[~2020-01-07 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 15:44 [PATCH] Documentation,selinux: fix references to old selinuxfs mount point Stephen Smalley
2020-01-07 16:19 ` Paul Moore [this message]
2020-01-07 16:35 Stephen Smalley
2020-01-07 18:00 ` 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=CAHC9VhQKZGa_g7Eq97WnUmzUAJDZoO5-sDhu1Qrxo7XRLjTPeA@mail.gmail.com \
    --to=paul@paul-moore.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=omosnace@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --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).