From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] autofs - comment on selinux changes needed for module autoload
Date: Mon, 21 May 2018 09:05:41 +0800 [thread overview]
Message-ID: <152686474171.6155.1239659539983577463.stgit@pluto.themaw.net> (raw)
Due to the autofs4 module using a file system type name of autofs
different from the module containing directory name autoload did
not function properly. To work around this kernel configurations
have often elected to build the module into the kernel.
This can result in selinux policies that prohibit autoloading of
the autofs module which need to be changed.
Add a comment about this to "possible changes" section of the
autofs4 module help.
Signed-off-by: Ian Kent <raven@themaw.net>
---
fs/autofs4/Kconfig | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/fs/autofs4/Kconfig b/fs/autofs4/Kconfig
index 2c2fdf989f90..99fda4d6da25 100644
--- a/fs/autofs4/Kconfig
+++ b/fs/autofs4/Kconfig
@@ -29,6 +29,12 @@ config AUTOFS4_FS
and the module name are the same as the file system name there
is no need to manually load module.
- any "alias autofs autofs4" will need to be removed.
+ - due to the autofs4 module directory name not being the same as
+ its file system name autoloading didn't work properly. Because
+ of this kernel configurations would often build the module into
+ the kernel. This may have resulted in selinux policies that will
+ prevent the autofs module from autoloading and will need to be
+ updated.
Please configure AUTOFS_FS instead of AUTOFS4_FS from now on.
reply other threads:[~2018-05-21 1:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=152686474171.6155.1239659539983577463.stgit@pluto.themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).