Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f8a9bc62 authored by Matthew Garrett's avatar Matthew Garrett Committed by James Morris
Browse files

security: constify some arrays in lockdown LSM 



No reason for these not to be const.

Signed-off-by: default avatarMatthew Garrett <mjg59@google.com>
Suggested-by: default avatarDavid Howells <dhowells@redhat.com>
Signed-off-by: default avatarJames Morris <jmorris@namei.org>
parent b602614a

security/lockdown/lockdown.c

+2 −2
Original line number Diff line number Diff line
@@ -16,7 +16,7 @@ 


static enum lockdown_reason kernel_locked_down;



static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = {

static const char *const lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = {

	[LOCKDOWN_NONE] = "none",

	[LOCKDOWN_MODULE_SIGNATURE] = "unsigned module loading",

	[LOCKDOWN_DEV_MEM] = "/dev/mem,kmem,port",
@@ -40,7 +40,7 @@ static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = { 
	[LOCKDOWN_CONFIDENTIALITY_MAX] = "confidentiality",

};



static enum lockdown_reason lockdown_levels[] = {LOCKDOWN_NONE,

static const enum lockdown_reason lockdown_levels[] = {LOCKDOWN_NONE,

						 LOCKDOWN_INTEGRITY_MAX,

						 LOCKDOWN_CONFIDENTIALITY_MAX};