From mboxrd@z Thu Jan  1 00:00:00 1970
From: jmorris@namei.org (James Morris)
Date: Thu, 6 Apr 2017 18:44:16 +1000 (AEST)
Subject: [PATCH 02/24] Add the ability to lock down access to the running
	kernel image
In-Reply-To: <149141221365.31282.16276273075946694481.stgit@warthog.procyon.org.uk>
References: <149141219387.31282.6648284836568938717.stgit@warthog.procyon.org.uk>
	<149141221365.31282.16276273075946694481.stgit@warthog.procyon.org.uk>
Message-ID: <alpine.LRH.2.20.1704061840090.12226@namei.org>
To: linux-security-module@vger.kernel.org
List-Id: linux-security-module.vger.kernel.org

On Wed, 5 Apr 2017, David Howells wrote:

> +#include <linux/security.h>
> +#include <linux/export.h>
> +
> +static __read_mostly bool kernel_locked_down;

How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not 
configured?


-- 
James Morris
<jmorris@namei.org>

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html