module/lsm: Have apparmor module parameters work with no args (5265fc62) · Commits · 戴 / test

The apparmor module parameters for param_ops_aabool and param_ops_aalockpolicy are both based off of the param_ops_bool, and can handle a NULL value passed in as val. Have it enable the new KERNEL_PARAM_FL_NOARGS flag to allow the parameters to be set without having to state "=y" or "=1". Cc: John Johansen <john.johansen@canonical.com> Signed-off-by:

Steven Rostedt <rostedt@goodmis.org> Signed-off-by:

Rusty Russell <rusty@rustcorp.com.au>

security/apparmor/lsm.c

+2 −0

Original line number	Diff line number	Diff line
		@@ -666,6 +666,7 @@ static int param_set_aabool(const char val, const struct kernel_param kp);
		static int param_get_aabool(char buffer, const struct kernel_param kp);
		#define param_check_aabool param_check_bool
		static struct kernel_param_ops param_ops_aabool = {
		.flags = KERNEL_PARAM_FL_NOARG,
		.set = param_set_aabool,
		.get = param_get_aabool
		};
		@@ -682,6 +683,7 @@ static int param_set_aalockpolicy(const char val, const struct kernel_param kp
		static int param_get_aalockpolicy(char buffer, const struct kernel_param kp);
		#define param_check_aalockpolicy param_check_bool
		static struct kernel_param_ops param_ops_aalockpolicy = {
		.flags = KERNEL_PARAM_FL_NOARG,
		.set = param_set_aalockpolicy,
		.get = param_get_aalockpolicy
		};

Admin message