[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e6e79af-a37f-c48e-5932-9b29270ac034@schaufler-ca.com>
Date: Mon, 13 Feb 2017 12:44:41 -0800
From: Casey Schaufler <casey@...aufler-ca.com>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>, jmorris@...ei.org,
linux-security-module@...r.kernel.org
Cc: kernel-hardening@...ts.openwall.com
Subject: Re: [RFC PATCH 1/4] security: mark LSM hooks as __ro_after_init
On 2/13/2017 2:33 AM, Tetsuo Handa wrote:
> James Morris wrote:
>> As the regsitration of LSMs is performed during init and then does
>> not change, we can mark all of the regsitration hooks as __ro_after_init.
>>
>> Signed-off-by: James Morris <james.l.morris@...cle.com>
> This patch makes LKM based LSMs (e.g. AKARI) impossible.
When a mechanism to do LKM based modules work is proposed
it could include ifdef's around the __ro_after_init. I'm
assuming that enabling LKM modules is something we'd want to
make optional.
> I'm not happy with this patch.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
