From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Kees Cook <keescook@chromium.org>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>,
Anna Schumaker <anna.schumaker@netapp.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mount.nfs: Protocol error after upgrade to linux/master
Date: Sat, 23 Mar 2019 11:44:12 +0900 [thread overview]
Message-ID: <47335573-08f1-0efc-e51a-e2b6a6b69a01@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CAGXu5jKVQ=-mdMWsefuNDagwF3pQEiosb4niRx-gBKCmRK_h-g@mail.gmail.com>
On 2019/03/23 7:45, Kees Cook wrote:
> It breaks the backward-compat for the "security=" line. If a system is
> booted with CONFIG_LSM="minors...,apparmor" and "security=selinux",
> neither apparmor nor selinux will be initialized. The logic on
> "security=..." depends on the other LSMs being present in the list.
Really? The logic on "security=..." does not depend on LSM_FLAG_LEGACY_MAJOR
LSMs being present in the CONFIG_LSM= list, for ordered_lsm_parse() does
(Step 1) Enable LSM_ORDER_FIRST module (i.e. capability).
(Step 2) Disable LSM_FLAG_LEGACY_MAJOR modules which was not specified
by "security=" parameter when "security=" parameter was specified.
(Step 3) Enable modules specified by "lsm=" parameter (or CONFIG_LSM= settings
if "lsm=" parameter was not specified).
(Step 4) Enable up to one LSM_FLAG_LEGACY_MAJOR module which was specified
by "security=" parameter when "security=" parameter was specified.
(Step 5) Disable all unused modules.
and (Step 4) will compensate for lack of that module in (Step 3).
prev parent reply other threads:[~2019-03-23 2:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190315110555.0807d015@cakuba.netronome.com>
[not found] ` <20190315120105.5541ad46@cakuba.netronome.com>
2019-03-15 23:54 ` Jakub Kicinski
2019-03-16 5:24 ` Kees Cook
2019-03-16 5:38 ` Kees Cook
2019-03-16 8:08 ` Tetsuo Handa
2019-03-17 1:02 ` Casey Schaufler
2019-03-19 10:56 ` Tetsuo Handa
2019-03-19 15:03 ` Casey Schaufler
2019-03-21 16:38 ` Kees Cook
2019-03-21 21:10 ` Tetsuo Handa
2019-03-22 22:45 ` Kees Cook
2019-03-23 2:44 ` Tetsuo Handa [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=47335573-08f1-0efc-e51a-e2b6a6b69a01@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=anna.schumaker@netapp.com \
--cc=casey@schaufler-ca.com \
--cc=jakub.kicinski@netronome.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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
all inboxes | Powered by JetHome®